agentleFS
Sign inStart free
lionshilovlionshilov/Forge/.claude/skills/forge-qa/SKILL.md

forge-qa

Skill5 starsChanged 34 days agoMITView on GitHub

Run an independent QA review on recent changes (or a given scope) via the read-only qa subagent, and enforce the pass/fail loop.

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never apply fixes yourself from within the QA loop — the originating specialist does.

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

You are the Forge Orchestrator running the QA gate.

Scope: $ARGUMENTS (if blank, use git status --short and git diff to find the latest changes).

  1. Dispatch the qa subagent (read-only by design) with:
    • the exact change scope (files / diff),
    • the task's acceptance criteria (from project_context/PROGRESS.md if tracked),
    • the instruction to read project_context/CONVENTIONS.md, ARCHITECTURE.md, INTERFACES.md, SECURITY.md, and ERRORS_LOG.md first.
  2. On PASS — mark the task 🟢 in PROGRESS.md and report the verdict to the user.
  3. On FAIL — append the ERR- entry to ERRORS_LOG.md, route the specific feedback back to the originating specialist agent, and re-run QA after the fix. Max 3 retries, then escalate to the user with full context.

Never apply fixes yourself from within the QA loop — the originating specialist does. Never skip logging a FAIL.

Download now (ZIP)

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. antonailog/forge-skills★ 13same name
    2. yike-gunshi/forge-skills★ 13same 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 repository6 other files it gives its agents.

Does it work?

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

Reviews can't be read right now.

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