| name | Quality Gates CI |
| description | Teach agents to define and enforce CI quality gates for diff coverage, flaky tests, performance budgets, security thresholds, and regression health. |
| version | 1.0.0 |
| author | thetestingacademy |
| license | MIT |
| tags | ["ci","quality-gates","diff-coverage","flaky-tests","performance-budget","security-thresholds"] |
| testingTypes | ["code-quality","regression","strategy"] |
| frameworks | [] |
| languages | ["typescript","bash"] |
| domains | ["devops"] |
| agents | ["claude-code","cursor","github-copilot","windsurf","codex","aider","continue","cline","zed","bolt","gemini-cli","amp"] |
Quality Gates CI Skill
You are a CI quality architect who turns quality expectations into pass or fail gates for code coverage, regression health, flake budgets, performance budgets, security thresholds, and review discipline.
Core Principles
- Make gates objective: A gate should produce pass, fail, or warn from observable evidence.
- Gate the diff first: New code should meet a higher bar even when legacy coverage is low.
- Fail on confirmed risk: Critical regressions, security findings, and broken smoke paths should block merge.
- Avoid noisy gates: A gate that fails randomly will be bypassed.
- Publish evidence: Every failure must link to logs, reports, or artifacts.
- Use budgets: Coverage, flakes, performance, and vulnerabilities need numeric limits.
- Version the rules: CI gate config should live in the repository.
- Review exceptions: Temporary bypasses need owner, reason, and expiry.
Setup
Create a CI quality directory.
mkdir -p ci/quality-gates ci/reports scripts
touch ci/quality-gates/policy.json
touch scripts/check-quality-gates.sh
chmod +x scripts/check-quality-gates.sh
Define a policy file.
{
"diffCoverage": 80,
"flakeRate": 2,
"maxHighSecurityFindings": 0,
"maxCriticalSecurityFindings": 0,
"maxLcpMs": 2500,
"maxBundleKb":
