quality-gates
Skill224 starsChanged 3 months agoMITView on GitHub
Run security and quality gates (secrets, SAST, deps, DAST, coverage, file-size) for any project. CI/CD-ready. Use before code review or push.
- Installs packages
We split this skill into the rules it gives an agent
4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 21 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
If invoked without arguments, use AskUserQuestion:
- Very specific: line 39
When /quality-gates setup is invoked:
- Very specific: line 118
/code-review: Run gates first, feed latest-report.md into review context - Very specific: line 119
/cook: Run gates before code review gate
“Common” is measured: kept by at least 6 in 10 of the 21 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
Language-agnostic security and quality scanning. Wraps gitleaks, trivy, semgrep, nuclei, SonarQube, and file-size checks.
Default (No Arguments)
If invoked without arguments, use AskUserQuestion:
| Option | Description |
setup | Claude wizard — reads docs, generates config, guides install |
run | Run all applicable gates |
report | Generate markdown report from last run |
Present via AskUserQuestion with header "Quality Gates", question "What would you like to do?".
Commands
| Command | Script | Description |
/quality-gates setup | wizard (Claude) | Full setup wizard — Load references/setup-wizard.md |
/quality-gates run | run-all.sh | Run all gates (blocked if setup incomplete) |
/quality-gates run --check <gate> | run-all.sh | Run one gate only |
/quality-gates run --no-block | run-all.sh | Print findings, always exit 0 |
/quality-gates run --json | run-all.sh | Machine-readable JSON summary |
/quality-gates run --mode <mode> | run-all.sh | Force run mode (pre-commit/pre-push/pr/ci/diff/full) |
/quality-gates report | report.sh | Generate markdown report from gate outputs |
Setup guard: run is blocked if .quality-gates/config.yaml is missing or required tools not installed. Use --no-block to override.
Setup Wizard
When /quality-gates setup is invoked:
Load references/setup-wizard.md and follow ALL steps in order.
Steps overview:
- Read project context — check
docs/first, ask user if missing [BLOCKING] - Ask optional gates — SonarQube, DAST (tags + blocking threshold), hooks [BLOCKING]
- Confirm with user — show full config summary [BLOCKING]
- Generate config — run
generate-config.sh - Setup validation — run
setup-all.sh --json - Install guidance — per missing tool
- Summary — print final status
Gate Reference
| Gate | Tool | Block condition | Scope |
secrets | gitleaks | exit 1 always | staged / diff / full history |
deps | trivy | exit 1 on CRITICAL, exit 2 on HIGH | lockfiles only |
sast | semgrep | exit 1 on ERROR, exit 2 on WARNING | diff-aware (BASE_SHA) |
dast | nuclei | exit 1 at block_severity threshold, exit 2 below | endpoints.txt (CI-only by default) |
coverage | bash/jq | exit 1 if below threshold | coverage report files |
file-size | tokei/wc | exit 2 only (warn, never block) | all dirs (scope.exclude applied) |
sonar | sonar-scanner | exit 1 if gate FAILED | full project (PR decoration: Developer Edition+) |
Exit Codes
| Code | Meaning |
| 0 | Pass |
| 1 | Hard block (error) |
| 2 | Warn only (non-blocking) |
| 3 | Tool not installed |
| 4 | Skipped (condition not met) |
Run Modes
Auto-detected. Override with QUALITY_GATES_MODE=<mode> or --mode <mode>.
| Mode | Auto-detected when | Scan scope |
pre-commit | QUALITY_GATES_SCOPE=pre-commit | staged files only |
pre-push | QUALITY_GATES_SCOPE=pre-push | upstream tracking branch |
pr | CI + PR env vars (GITHUB_BASE_REF etc.) | merge-base with PR target |
ci | CI env set, no PR | full scan |
diff | local default | merge-base with origin/main |
full | QUALITY_GATES_MODE=full | full scan |
Override baseline: BASE_SHA=<sha> /quality-gates run
Output Format
🔍 Running Quality Gates...
[secrets] ✅ gitleaks: no secrets found
[deps] ⚠️ trivy: not installed → brew install trivy
[sast] ❌ semgrep: 2 ERROR findings → .quality-gates/reports/raw/20260329-181500/sast-report.json
[file-size] ⚠️ 3 files exceed 200 LOC
[coverage] ✅ 78% (threshold: 70%)
[sonar] ℹ️ Skipped (SONAR_HOST_URL not set)
[dast] ℹ️ Skipped (CI only)
────────────────────────────────
Summary: 1 error, 2 warnings, 2 skippedConfiguration
Config: .quality-gates/config.yaml (created by setup wizard).
Template: .claude/skills/quality-gates/templates/quality-gates-config.yaml.
Key fields: scope.exclude, thresholds.coverage, thresholds.file_max_loc, dast.tags, dast.block_severity, gates.<name>.enabled.
Integration
- Pre-commit: secrets check only (fast, hard block)
- Pre-push: secrets + sast + deps (via
QUALITY_GATES_SCOPE=pre-push) - CI pipeline: Full run including DAST + SonarQube
/code-review: Run gates first, feedlatest-report.mdinto review context/cook: Run gates before code review gate
References
| File | Purpose |
references/setup-wizard.md | Full 9-step wizard execution (load when running setup) |
references/archetype-table.md | Archetype presets + customization signals + SonarQube profiles |
references/nuclei-templates-catalog.md | Signal → nuclei tags/profiles |
references/sonar-properties-reference.md | Per-stack sonar-project.properties |
references/gitleaks-rules-reference.md | Custom gitleaks rules + allowlists |
Other versions23 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 23
- andymai/gridfinity-layout-tool★ 438same name
- andymai/brepjs★ 128same name
- NoobyGains/godmode★ 115same name
- cubetribe/ClaudeCode_GodMode-On★ 53same name
- Kanevry/session-orchestrator★ 53same name
- microsoft/github-copilot-modernization★ 48same name
- NikiforovAll/lazyclaude★ 41same name
- sampleXbro/agentsmesh★ 24same name
- wpank/ai★ 11same name
- mxrsv/agents-skills★ 9same name
13 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 repository46 other files it gives its agents.
- .claude/skills/react-best-practices/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ai-multimodalSkill
- askSkill
- backend-developmentSkill
- brainstorm-featuresSkill
- brainstorm-technicalSkill
- chrome-devtoolsSkill
- code-reviewSkill
- context-engineeringSkill
- cookSkill
- databasesSkill
- debugSkill
- design-mockup-createSkill
- design-systemSkill
- devopsSkill
- docs-seekerSkill
- docsSkill
- fixSkill
- frontend-designSkill
- frontend-developmentSkill
- gitSkill
- journalSkill
- markdown-novel-viewerSkill
- mermaidjs-v11Skill
- mobile-developmentSkill
- plans-kanbanSkill
- planSkill
- previewSkill
- problem-solvingSkill
- project-managementSkill
- react-best-practicesSkill
- repomixSkill
- researchSkill
- scoutSkill
- sequential-thinkingSkill
- skill-creatorSkill
- specsSkill
- teamSkill
- test-casesSkill
- testSkill
- ui-stylingSkill
- ui-ux-pro-maxSkill
- web-design-guidelinesSkill
- web-frameworksSkill
- web-testingSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

