quality-gates
Skill0 starsChanged 18 days agoMITView on GitHub
Set up a project with automated code-smell and quality gates — git pre-commit (fast) and pre-push (slow) hooks that run format, lint, complexity, duplication, dead-code, type, and test checks. Language-agnostic; detects the stack and wires the idiomatic tools. Use when asked to add quality gates, code-smell detection, linting/complexity checks, or git hooks to a repo.
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
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 repository11 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- analytics-viewSkill
- explain-diffSkill
- finalizeSkill
- frontend-designSkill
- planSkill
- pr-reviewSkill
- prSkill
- rule-authoringSkill
- setup-projectSkill
- test-on-mainSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 24 edited versions we read keep these.
2
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 16
Ensure every language has a tool for each capability.
- Distinctive: line 51
Run the pre-commit and pre-push scripts once manually.
“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
Deterministic linters catch measurable smells (complexity, duplication, dead code) every commit; LLM review handles semantic ones. Set up the linter tiers below.
1. Detect the stack
Inspect the repo root: package.json → TS/JS, pyproject.toml/setup.cfg → Python, go.mod → Go, Cargo.toml → Rust, etc. A repo may have several. For each, find existing scripts/config before adding anything — reuse them.
2. Fill the capability matrix per language
Ensure every language has a tool for each capability. Enable complexity, duplication, and dead-code explicitly — usually off by default.
| Capability | TS/JS | Python | Any language |
| format | prettier | ruff format | the idiomatic formatter |
| lint | oxlint | ruff (E,F,B,SIM,PL) | the idiomatic linter |
| complexity | oxlint complexity rule | ruff C901 + PL | linter's cyclomatic/cognitive rule, threshold ~10 |
| duplication | jscpd | jscpd | jscpd (language-agnostic) |
| dead code | knip | ruff F401/vulture | unused-export/dead-code tool |
| types | tsc | mypy/pyright (if used) | the type checker |
| tests | vitest/bun | pytest | the test runner |
For unknown languages, use the community-standard tool rather than inventing config.
3. Split fast vs slow
- pre-commit (fast, staged files only): format check, lint, complexity, duplication.
- pre-push (slow, whole repo): type check, tests, dead-code scan.
4. Install versioned git hooks
Copy templates/git-hooks/ (at ../../templates/ from this skill's base directory) into the repo's .githooks/, then point git at it:
mkdir -p .githooks && cp <skill-dir>/../../templates/git-hooks/pre-commit <skill-dir>/../../templates/git-hooks/pre-push .githooks/
chmod +x .githooks/*
git config core.hooksPath .githooksEdit the two scripts so their command blocks match the tools from step 2. The templates auto-detect TS/Python; add a block per additional language.
5. Add unified scripts and baseline
Wire a check (all tiers) and check:fix entry point in the project's task runner so hooks and humans share one command. Set a baseline (jscpd --threshold, linter --max-warnings) or fix-then-enforce so no gate always fails.
6. Verify
Run the pre-commit and pre-push scripts once manually; confirm they pass on a clean tree and fail on an injected smell.
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.