quality-gates

Automated quality gates run a canonical sequence of type checks, linting, tests, and verification handoff after code changes to validate correctness. The workflow discovers existing checks, executes them in order, and updates the workflow state for traceability.

When a quality gate fails, the workflow captures the exact failure, diagnoses the root cause, suggests next steps, and updates the workflow state to maintain traceability. This ensures code changes are not introducing regressions without clear evidence and remediation guidance.

Yes, automated quality gates can execute type checks, linting, tests, and verification handoff across multiple projects and languages. The workflow discovers which checks exist in the repository and executes them in canonical order regardless of the specific language or project structure.

The workflow discovers available gates in the repository and marks missing checks as not-applicable with specific reasons. This ensures the canonical gate sequence maintains a unified quality verdict without failing incorrectly when a particular type of check is not configured.

You should run automated linting and type checks immediately after implementing changes to validate correctness and prevent regressions. Running the canonical gate sequence at this stage ensures all checks pass before code is handed off or merged into the main branch.