verification-loop

A pre-commit verification pipeline sequentially checks build, type checking, linting, testing, security scanning, and diff review. This fail-stop process prevents unverified code from entering the repository by halting progress immediately when issues are detected.

Sequential gatekeeping is a fail-stop quality assurance mechanism that only lets the next verification stage run once the previous one passes. It stops build failures, type errors, lint issues, test failures, or security vulnerabilities from slipping into commits.

To stop unverified refactoring changes from entering a repository, enforce a complete verification pipeline that checks compilation, types, linting, tests, security, and diff review. This fail-stop approach ensures regressions are kept out of milestone checkpoints and pre-PR reviews.

Pre-PR review requires structured reporting to capture pass or fail status, issue counts, and skipped tools. This provides a precise determination of whether changes are READY or NOT READY after running security scans and test failures.

A fail-stop quality gate is needed for feature completion, major refactors, pre-commit reviews, and milestone checkpoints. It ensures fresh verification of compilation, types, linting, tests, and security before declaring any work ready.

Skipping lint or type checking stages is prevented by sequential gatekeeping. The pipeline only advances to the next stage once the previous one passes, requiring build, type check, lint, test, security scan, and diff review to all complete successfully.