quality-gates

Automated code quality gates enforce consistent typechecking, testing, and linting before commits to detect regressions. They apply blocking checks at session end and require all configured commands to pass, reducing release risk in agent-driven workflows.

Incremental quality checks run tests on changed files and typechecks after implementation waves to surface regressions early. This non-blocking approach creates follow-up tasks for failing checks without halting the active development session.

Quality gates respect configurable session fields for test-command, typecheck-command, and lint-command. You define the specific commands your project uses, and the checks execute those exact scripts during baseline, incremental, full gate, and per-file validation phases.

Quality checks gracefully degrade when tools are missing by automatically skipping the unavailable check and noting its absence. This prevents the session from failing outright, allowing remaining configured checks to execute successfully.

Baseline checks perform quick non-blocking health scans at session start to capture a reference state, while full gate checks are blocking validations at session end requiring typecheck, tests, and lint to pass before commit.

Per-file quality checks work within session orchestration to let reviewers validate specific changed files. They run targeted typechecking, testing, and linting on individual files rather than executing checks across the entire project codebase.