quality-gate

Coordinate quality checks across tiered gates in CI/CD pipelines.

3|2|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/robotijn/ctoc --skill quality-gate-robotijn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality-gate
Source: https://github.com/robotijn/ctoc/tree/main/skills/quality/quality-gate
Command: npx skills add https://github.com/robotijn/ctoc --skill quality-gate-robotijn

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about quality-gate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce zero-warning builds and block code regressions in a CI/CD pipeline?

You can enforce zero-warning builds and block code regressions by integrating tiered quality gates into your CI/CD pipeline. It coordinates checks across lint, typecheck, tests, and security to automatically block pull request merges on failures.

What is baseline-vs-delta gating and how does it handle legacy code warnings?

Baseline-vs-delta gating tracks accepted exceptions with mandatory expiry dates and only blocks code regressions against the persisted baseline rather than absolute thresholds, preventing legacy codebases from breaking the build.

Does this quality gate integration support GitHub Actions, GitLab CI, and CircleCI?

Yes, this quality gate integration natively supports GitHub Actions, GitLab CI, and CircleCI. It provides pre-configured fail-on-warning settings for 7 programming languages to validate pull requests.

How do I configure pull request validation to run multiple quality checks within a time budget?

Configure pull request validation by orchestrating 10 quality gate categories across 4 tiers, enforcing a 5 to 10 minute PR gate budget to prevent developer context-switching while checking complexity, coverage, and CVEs.

Can I use tiered quality enforcement to separate blocking checks from review-only checks?

Yes, you can use tiered quality enforcement to separate blocking Tier 1 checks like lint and type errors from review Tier 3 checks, ensuring only critical failures block merges while still tracking accessibility and performance.

Why do my pull request quality gates keep failing on pre-existing technical debt?

Pull request quality gates often fail on pre-existing debt because absolute thresholds break legacy codebases. Using baseline-vs-delta gating with mandatory exception expiry dates avoids permanent debt amnesty while blocking only new regressions.