Quality Gates

Enforce quality checkpoints at every stage of the development lifecycle. Each gate defines what is checked, when it runs, and whether it blocks progression.

When to Use

• Before committing — catch lint errors, formatting issues, type errors, and secrets before they enter history
• Before merging — ensure full test suites pass, coverage thresholds are met, and code has been reviewed
• Before deploying — validate integration tests, security scans, and performance budgets in staging
• During code review — verify that all automated gates have passed and manual review criteria are satisfied
• After deploying — monitor health checks, error rates, and performance baselines

Gate Overview