quality-check
Skill9 starsChanged 3 months agoMITView on GitHub
Unified quality gate dispatcher. Runs selected quality checks with profile-aware defaults.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- emergent-wisdom/understanding-graphtheir own version, first seen Nov 1, 2026
- AlekseiUL/heisenberg-team-GPTtheir own version, first seen Nov 1, 2026
- AlekseiUL/heisenberg-teamtheir own version, first seen Nov 1, 2026
- neeldas1209/GTM-Strategy-Enginetheir own version, first seen Oct 20, 2026
- prPMDev/my-portfolio-kittheir own version, first seen Oct 13, 2026
- hsnice16/agent-friendly-codetheir own version, first seen Oct 11, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- dlupiak/claude-session-dashboard★ 66same name
- AlekseiUL/heisenberg-team★ 17same name
- AlekseiUL/heisenberg-team-GPT★ 9same name
- MainFrame100/quality-check-skill★ 7same name
- hsnice16/agent-friendly-code★ 2same name
- prPMDev/my-portfolio-kit★ 2same name
- emergent-wisdom/understanding-graph★ 1same name
- Evan-Kim2028/agent-skills★ 1same name
- bloxy-studios/shorts-studio★ 0same name
- neeldas1209/GTM-Strategy-Engine★ 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 repository56 other files it gives its agents.
- .claude/agents/CLAUDE.mdCLAUDE.md
- .claude/hooks/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .claude/prompts/CLAUDE.mdCLAUDE.md
- .claude/rules/CLAUDE.mdCLAUDE.md
- .claude/skills/CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- vision/CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- scaffold/llms.txtllms.txt
- architecture-checkSkill
- backlog-reviewSkill
- bootstrapSkill
- brainstormSkill
- buildSkill
- claude-sense-checkSkill
- code-qualitySkill
- commitSkill
- continueSkill
- custom-hooksSkill
- dashboardSkill
- debug-sessionSkill
- deploySkill
- discoverSkill
- doctorSkill
- fix-issueSkill
- framework-upgradeSkill
- handoffSkill
- help-meSkill
- ideateSkill
- lanesSkill
- manual-testSkill
- merge-downSkill
- merge-upSkill
- optimizeSkill
- parallel-workSkill
- performance-checkSkill
- phase-reviewSkill
- pr-statusSkill
- quickstartSkill
- refine-loopSkill
- researchSkill
- retrospectiveSkill
- security-auditSkill
- skill-createSkill
- skill-evalSkill
- sprint-endSkill
- sprint-startSkill
- story-cycleSkill
- testing-cycleSkill
- test-validatorSkill
- UAT-cycleSkill
- undo-workSkill
- uninstallSkill
- weekly-maintenanceSkill
- wrap-upSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 6 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 34
If NO flags are provided, read the project profile from the Profile: line in CLAUDE.md and apply defaults:
- Distinctive: line 42
If the profile is not set or not recognized, default to standard behavior.
- Very specific: line 46
Before dispatching agent skills, run the quality-gate-sequence micro-component from .claude/prompts/quality-gate-sequence.md — this runs …
- Distinctive: line 48
HARD GATE: If tests fail, stop here. Do not dispatch agent skills on failing code.
- Distinctive: line 60
Run all selected checks in parallel for efficiency.
- Very specific: line 94
If FAIL: list the specific blocking findings with file:line references so the caller can address them.
- Distinctive: line 98
If a dispatched agent fails or times out: report that check as WARN with "agent failed — manual review recommended"
- Distinctive: line 99
If no checks are selected and profile cannot be determined: fall back to standard defaults (code + tests + security)
- Distinctive: line 100
If CLAUDE.md Commands has no test command configured: skip the test gate in quality-gate-sequence, note in report
“Common” is measured: kept by at least 6 in 10 of the 8 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-check
Running quality gates: $ARGUMENTS
1. Parse Flags
Extract check selection from $ARGUMENTS:
| Flag | Dispatches |
--code | /code-quality |
--tests | /test-validator |
--security | /security-audit |
--architecture | /architecture-check |
--performance | /performance-check |
--all | All 5 checks above |
2. Apply Profile Defaults
If NO flags are provided, read the project profile from the **Profile:** line in CLAUDE.md and apply defaults:
| Profile | Default Checks |
| lean | --code (lint + complexity only) |
| standard | --code --tests --security |
| strict | --all plus integration-tester agent |
If the profile is not set or not recognized, default to standard behavior.
3. Run Quality-Gate-Sequence First
Before dispatching agent skills, run the quality-gate-sequence micro-component from .claude/prompts/quality-gate-sequence.md — this runs lint, typecheck, and tests from CLAUDE.md Commands. These are fast, deterministic checks that catch issues before the more expensive agent analysis.
HARD GATE: If tests fail, stop here. Do not dispatch agent skills on failing code.
4. Dispatch Selected Checks
Dispatch each selected check as a parallel Task agent. Each invokes the corresponding skill:
For each selected check:
Launch Agent (subagent_type: general-purpose) with prompt:
"Run /<skill-name> on the current codebase. Return a structured report."Run all selected checks in parallel for efficiency. Wait for all to complete.
<IF condition="Profile is strict AND --all was selected (explicitly or via default)">
Also dispatch the `integration-tester` native agent (`.claude/agents/integration-tester.md`) to independently verify acceptance criteria by running commands.
</IF>5. Unified Report
Combine results from all dispatched checks into a single report:
## Quality Gate Report
| Check | Status | Key Findings |
|-------|--------|-------------|
| Code Quality | PASS/WARN/FAIL | [summary] |
| Test Validator | PASS/WARN/FAIL | [summary] |
| Security Audit | PASS/WARN/FAIL | [summary] |
| Architecture | PASS/WARN/FAIL/SKIP | [summary] |
| Performance | PASS/WARN/FAIL/SKIP | [summary] |
| Integration Test | PASS/WARN/FAIL/SKIP | [summary] |
**Overall: PASS / WARN / FAIL**Verdict rules:
- PASS — all checks pass with no blocking findings
- WARN — advisory findings only (no blocking issues)
- FAIL — one or more checks have blocking findings
6. Return Verdict
Return the unified report and overall verdict. Callers (sprint-end, story-cycle) use this verdict for gate decisions.
If FAIL: list the specific blocking findings with file:line references so the caller can address them.
Error Handling
- If a dispatched agent fails or times out: report that check as WARN with "agent failed — manual review recommended"
- If no checks are selected and profile cannot be determined: fall back to standard defaults (code + tests + security)
- If CLAUDE.md Commands has no test command configured: skip the test gate in quality-gate-sequence, note in report
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.

