quality-gates
Skill0 starsChanged 7 months agoMITView on GitHub
Use PROACTIVELY when: completing tasks, before merging, after implementation, checking acceptance criteria. Provides quality gate checkpoints.
26 other projects use a version of this.
Adopted by
Most recently taken up by
- cormacc/dotagentstheir own version, first seen Nov 8, 2026
- pentoai/quality-gates-skillstheir own version, first seen Nov 8, 2026
- MMACABRE/SKILLStheir own version, first seen Nov 8, 2026
- mxrsv/agents-skillstheir own version, first seen Nov 1, 2026
- NoobyGains/godmodetheir own version, first seen Nov 1, 2026
- rubenmarcus/agent-skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use plan.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
BlockSkillplan
Draft a TDD, PRD, or lightweight plan in the conversation without committing it.
Also in 3 projects that use this
Other versions26 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 26
- andymai/gridfinity-layout-tool★ 525same name
- typv/nest-turbo-starter★ 224same name
- andymai/brepjs★ 140same name
- NoobyGains/godmode★ 118same name
- cubetribe/ClaudeCode_GodMode-On★ 53same name
- Kanevry/session-orchestrator★ 53same name
- microsoft/github-copilot-modernization★ 48same name
- NikiforovAll/lazyclaude★ 41same name
- sampleXbro/agentsmesh★ 27same name
- mxrsv/agents-skills★ 11same name
16 more not listed
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 repository17 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agent-detectionSkill
- auto-delegationSkill
- bookstackSkill
- delegatorSkill
- faceswapSkill
- git-standardsSkill
- headswapSkill
- health-dashboardSkill
- imageSkill
- motionSkill
- multi-terminalSkill
- project-docsSkill
- safety-gateSkill
- upscaleSkill
- videoSkill
- web-researchSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 24 edited versions we read keep these.
4
Distinctive
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
- Distinctive: line 23
Trigger: Before starting implementation
- Distinctive: line 46
Trigger: After implementation complete
- Distinctive: line 69
Trigger: Before deployment/merge
- Distinctive: line 85
Create security remediation tasks
“Common” is measured: kept by at least 6 in 10 of the 24 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Quality Gates Skill
This skill provides quality gate checklists for critical workflow transitions.
Gate Overview
| Gate | When | Who Reviews | Purpose |
| Pre-Implementation | After spec, before coding | architect | Design review |
| Post-Implementation | After coding, before merge | quality | Code review |
| Pre-Release | Before deployment | security | Security audit |
Pre-Implementation Gate
Trigger: Before starting implementation
Reviewer: architect
Checklist
- Spec is architecturally sound
- Dependencies identified
- Tech stack aligned
- Scope is realistic
- No security anti-patterns
- Data flow considered
On Failure
- Pause and report to user
- User can override
- Or: Revise spec
Post-Implementation Gate
Trigger: After implementation complete
Reviewer: quality agent or superpowers:requesting-code-review
Checklist
- All acceptance criteria met
- Tests passing
- Coverage adequate (>80%)
- No linting errors
- Documentation updated
- No obvious tech debt
On Failure
- Create remediation tasks
- Fix issues
- Re-run gate
Pre-Release Gate
Trigger: Before deployment/merge
Reviewer: security, then user
Security Checks
- No new vulnerabilities
- Secrets not exposed
- Dependency CVEs addressed
- GDPR compliance verified
User Checks
- Acceptance criteria fulfilled
- Manual review completed
On Failure
- Create security remediation tasks
- Main chat coordinates fixes
- Re-run gate
Using Gates with Superpowers
CWE quality gates integrate with superpowers:
| Gate | Superpowers Skill |
| Pre-Implementation | superpowers:brainstorming |
| Post-Implementation | superpowers:verification-before-completion |
| Code Review | superpowers:requesting-code-review |
Quick Reference
Before coding → Check design with architect
After coding → Verify with quality/superpowers
Before merge → Security audit + user approvalDoes 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.