What problem does it solve?
It reduces the risk of broken builds, failing tests, and missing security checks by enforcing a repeatable verification sequence before code is merged.
Core Features & Use Cases
- Build verification: Confirms the project compiles successfully using the repo’s build command.
- Quality checks: Runs type checking and linting to catch correctness and style issues early.
- Confidence checks: Executes the test suite with coverage expectations and performs lightweight security scanning (secrets and debug output).
- Change awareness: Reviews the diff summary to ensure modifications are intentional and reviewable.
- Use case: You refactor a critical module and want to ensure the build still passes, TypeScript types stay consistent, linting remains clean, tests still pass with acceptable coverage, and no accidental secrets or console logging were introduced.
Quick Start
Run verification before opening your pull request after completing a significant change in your repository.