Menu
Run an independent QA review on recent changes (or a given scope) via the read-only qa subagent, and enforce the pass/fail loop.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
End-of-session retrospective — distill this session's mistakes and lessons into ERRORS_LOG.md, CONVENTIONS.md, and agent anti-pattern lists so the system learns across runs.
Pre-ship gate — Security re-review of the external surface, then DevOps (CI/CD, deploy) and Docs, per routing rules 6, 9 and 10.
Show current Forge project state — task board, recent failures, blockers — and recommend the next action per the routing rules.
Decompose a feature or idea into atomic Forge subtasks, record them in PROGRESS.md, and dispatch them per the routing rules.
| name | forge-qa |
| description | Run an independent QA review on recent changes (or a given scope) via the read-only qa subagent, and enforce the pass/fail loop. |
| argument-hint | ["files","task ID","or blank for latest changes"] |
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).
qa subagent (read-only by design) with:
project_context/PROGRESS.md if tracked),project_context/CONVENTIONS.md, ARCHITECTURE.md, INTERFACES.md, SECURITY.md, and ERRORS_LOG.md first.PROGRESS.md and report the verdict to the user.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.