verification-gates

Mandatory testing and linting enforcement blocks task completion until verification gates pass. It runs tests, type checks, linting, builds, and security validations, requiring fail-fast behavior with structured results output before changes are considered complete.

Pre-commit security scanning and type checks detect the project type to run appropriate tooling checks. It supports environments like Node.js, Python, Go, and Rust by routing commands specific to the detected stack.

The best way to handle flaky tests and timeouts during quality gate checks is applying a retry policy. The verification system uses fail-fast behavior with structured results and retries flaky or timeout failures before escalating.

Verification gate routing handles security-sensitive changes by triggering credential scanning, permission checks, and dependency audits. It uses an executor/verifier flow to escalate scrutiny and classify failures by severity like CRITICAL or BLOCKING.

To override or skip a blocking quality gate failure, you must follow documented override handling requirements. The system classifies failures by severity and explicitly documents when skipping gates is allowed and what escalation is required.