qa-gate
Skill16 starsChanged 37 days agoMITView on GitHub
Adversarial final gate before a release tool may run — re-run the suites, score six rubric dimensions, and emit APPROVED/CHANGES_REQUIRED/REJECTED. The qa-gate stage (H3/H5).
6 other projects use a version of this.
Adopted by
Most recently taken up by
- GeorgeAuth26/authentalink-playbooktheir own version, first seen Nov 8, 2026
- weedmo/skillstheir own version, first seen Nov 8, 2026
- mementomori-co/maker-masterytheir own version, first seen Oct 25, 2026
- ZachArticulateV/designer-pro-and-seotheir own version, first seen Oct 19, 2026
- victoraguilarsantamariadev/qa-exploretheir own version, first seen Sep 28, 2026
- Daniellaguips/ai-agent-ostheir own version, first seen Jun 10, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- ZachArticulateV/designer-pro-and-seo★ 10same name
- mementomori-co/maker-mastery★ 2same name
- victoraguilarsantamariadev/qa-explore★ 2same name
- GeorgeAuth26/authentalink-playbook★ 1same name
- weedmo/skills★ 1same name
- Daniellaguips/ai-agent-os★ 0same 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 repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- analyze-requirementsSkill
- be-fe-security-auditSkill
- commit-deploy-logSkill
- deep-researchSkill
- deploy-to-testSkill
- evidence-bundleSkill
- fanSkill
- fix-and-verifySkill
- impact-reviewSkill
- implement-changeSkill
- run-affected-testsSkill
- verify-implementationSkill
- verify-requestSkill
The file
Files
qa-gate
The qa-gate node of the DAG (review profile) — the last stage before a release tool may run, and the one the deny hook actually keys off.
Deliberately a second, adversarial review rather than a stamp on the first.
verification and qa-gate differ in stance, not in depth: verification asks
"does this meet the criteria", qa-gate assumes it does not and goes looking.
Feeds gate_rules.qa_gate_rejected: halt_for_human — unlike a verification
CHANGES_REQUIRED, which loops back to analysis automatically, a REJECTED here
stops the pipeline for a person. By this point the work has passed analysis,
implementation, test and verification; if it is still wrong, the loop is not what
is broken.
Honest about enforcement (C10): the hook reading this verdict is local defense-in-depth. A determined caller bypasses it. The real boundary for release-affecting actions is server-side at the gateway — this stage raises the cost of shipping something unverified, it does not make it impossible.
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
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.