What problem does it solve?
Manual, inconsistent quality checks often let warnings, regressions, and security issues slip into production, leading to costly post-release fixes and technical debt accumulation. This Skill eliminates that risk by centralizing all quality gate coordination and enforcing strict, automated pass/fail rules across every stage of development.
Core Features & Use Cases
- Multi-Tier Quality Enforcement: Coordinates 10 quality gate categories across 4 tiers (blocking Tier 1, warning-but-block-on-regression Tier 2, review Tier 3, CI-only Tier 4) covering lint, type checks, tests, coverage, complexity, security, CVEs, license compliance, performance, and accessibility.
- Baseline-Vs-Delta Gating: Tracks accepted exceptions with mandatory expiry dates to avoid permanent debt amnesty, and only blocks on regressions against the persisted baseline rather than absolute thresholds that break legacy codebases.
- CI/CD Integration: Natively supports GitHub Actions, GitLab CI, and CircleCI with pre-configured fail-on-warning settings for 7 programming languages, and enforces a 5–10 minute PR gate budget to avoid developer context-switching.
- Use Case: A development team can use this Skill to automatically run all quality checks on every pull request, block merges if any Tier 1 gate fails (e.g., lint warnings, type errors, failing tests), and get actionable, specific failure messages that name the exact failing gate, threshold, and baseline delta.
Quick Start
Use the quality-gate skill to run all quality checks on your current code branch, get a clear pass/fail decision with specific baseline regression details, and enforce zero-warning build policies across your CI pipeline.