Update QA Rules

Locate, draft, and apply QA rule updates in repository documents.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill update-qa-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Update QA Rules
Source: https://github.com/BedaBeda-Growth/bedabeda-growth-site/tree/main/skills/update-qa-rules
Command: npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill update-qa-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams update QA rules in the repository to reflect business constraints and ensure compliance.

Core Features & Use Cases

  • Locate the active QA rules document in the current repository (usually .agents/workflows/qa-rules.md or .agents/workflows/rules.md) and review its current format.
  • Draft precise updates that enforce the new constraint and include validation steps to verify changes.
  • Apply the changes to the document and provide a concise summary of the update and its verification.

Quick Start

Locate the active QA rules document, draft a precise update enforcing the new constraint, and apply the change to the repository.

Frequently Asked Questions about Update QA Rules

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update QA rules in a repository to enforce new compliance constraints?

To update QA rules, you locate the active document in your repository, draft precise modifications enforcing the new constraint, apply the changes, and generate a verification summary.

What is the standard file path for storing QA rules documentation?

QA rules documentation is typically located at .agents/workflows/qa-rules.md or .agents/workflows/rules.md within the repository.

How do I draft precise updates to modify existing QA policies without breaking workflows?

Drafting precise updates involves reviewing the current format of the QA rules document and writing modifications that include validation steps to verify the changes.

Can I mandate a specific behavior across multiple projects using a single QA rules update?

Yes, you can mandate specific behaviors across projects by applying targeted updates to the central QA rules document, ensuring the new constraint is enforced and validated.

What is the best way to verify that newly added QA rules are properly enforced?

The best way to verify newly added QA rules is to draft updates that include validation steps, apply the changes, and review the concise summary reporting the verification.