agentleFS
Sign inStart free
Guild-AgentsGuild-Agents/guild/.claude/skills/qa-cycle/SKILL.md

qa-cycle

Skill4 starsChanged 5 months agoMITView on GitHub

QA + bugfix cycle until it passes

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. DrunkenDealer/claude-code-qa-cycle★ 3same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository8 other files it gives its agents.

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. About 0 are common, 8 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After implementing changes that need validation

    line 38
  2. Distinctive:

    Before invoking the QA agent, run the project verification commands.

    line 50
  3. Very specific:

    Run project tests (e.g., npm test) — record result and output

    line 52
  4. Very specific:

    Run project lint (e.g., npm run lint) — record result and output

    line 53
  5. Distinctive:

    If any fail, this becomes input for the QA report as an automatic Blocker bug

    line 54
  6. Very specific:

    Read .claude/agents/qa.md to assume the QA role

    line 60
  7. Distinctive:

    Read CLAUDE.md for context

    line 61
  8. Distinctive:

    If tests or lint failed, include them as Blocker bugs in the report

    line 63
  9. Very specific:

    If QA reports bugs (including test/lint failures), invoke the Bugfix agent using Task tool with model: "sonnet" (execution tier):

    line 70
  10. Very specific:

    Read .claude/agents/bugfix.md to assume the Bugfix role

    line 72
  11. Distinctive:

    Verify that the fix resolves the issue

    line 76
  12. Distinctive:

    Run tests and lint to confirm no regressions were introduced

    line 77
  13. Distinctive:

    Approved: All criteria pass, no pending bugs

    line 88
  14. Very specific:

    When spawning QA or Bugfix agents via the Task tool, always use subagent_type: "general-purpose".

    line 106

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

QA Cycle

Runs a QA validation cycle followed by bugfix until all criteria pass clean. Useful for validating implementations without the full build-feature pipeline.

When to use

  • After implementing changes that need validation
  • To verify that a bug fix did not introduce regressions
  • As a final cycle before creating a PR

Usage

/qa-cycle

Process

Step 1 — Automated verification (mandatory)

Before invoking the QA agent, run the project verification commands. The specific commands are in the "CLI commands" section of CLAUDE.md:

  1. Run project tests (e.g., npm test) — record result and output
  2. Run project lint (e.g., npm run lint) — record result and output
  3. If any fail, this becomes input for the QA report as an automatic Blocker bug

Step 2 — QA Validation

Invoke the QA agent using Task tool with model: "sonnet" (execution tier):

  1. Read .claude/agents/qa.md to assume the QA role
  2. Read CLAUDE.md for context
  3. Receive the test and lint results from Step 1
  4. If tests or lint failed, include them as Blocker bugs in the report
  5. Review the acceptance criteria for the current task (if provided)
  6. Validate edge cases and error scenarios
  7. Report results

Step 3 — Bugfix (if there are bugs)

If QA reports bugs (including test/lint failures), invoke the Bugfix agent using Task tool with model: "sonnet" (execution tier):

  1. Read .claude/agents/bugfix.md to assume the Bugfix role
  2. Receive the QA bug report as input
  3. Diagnose the root cause of each bug
  4. Implement the minimal fix
  5. Verify that the fix resolves the issue
  6. Run tests and lint to confirm no regressions were introduced

Step 4 — Re-validation

Return to Step 1 (automated verification) to re-validate after the bugfix. Maximum 3 verification-QA-bugfix cycles to prevent infinite loops.

Step 5 — Final result

Present the result:

  • Approved: All criteria pass, no pending bugs
  • With warnings: Passes but there are minor warnings
  • Rejected: There are critical bugs that could not be resolved — escalate to the Tech Lead

Example Session

User: /qa-cycle

QA (sonnet) — Cycle 1: 2 of 5 criteria pass. Bug: form validation missing on email field.
Bugfix (sonnet) — Added email regex validation to UserForm component.
QA (sonnet) — Cycle 2: 5 of 5 criteria pass. 0 bugs.

Result: Approved.

Subagent Configuration

When spawning QA or Bugfix agents via the Task tool, always use subagent_type: "general-purpose". Guild agent role names are NOT valid Claude Code subagent_types.

Example:

Task tool with:
  subagent_type: "general-purpose"
  model: "sonnet"
  prompt: "Read .claude/agents/qa.md and assume that role. Then: [task description]"

The model parameter is resolved from the step's model-tier: qa-validate and bugfix use execution→"sonnet".

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free