verification-loop

Automated verification runs build, type-check, lint, test, security scan, and diff review phases sequentially before PRs. It executes explicit commands like npm run build to detect issues and stops on failure, ensuring code meets quality gates.

An automated verification loop is a structured workflow that validates code sessions across build, type, lint, test coverage, and security dimensions. It reduces regression risk and manual review workload by enforcing quality gates before releases.

Yes, the type and static analysis phase runs checks for both TypeScript and Python projects. This catches type errors early in the development cycle alongside lint and style enforcement across multiple languages.

The security scan phase checks for exposed secrets, while the diff review phase catches unintended changes by examining code differences. Both run automatically as part of the multi-phase verification workflow before PRs.

Yes, the test suite phase runs tests with coverage reporting to verify that thresholds are met. It highlights coverage gaps to guarantee feature readiness before significant changes are merged or released.

If the build verification fails using npm run build or pnpm build, the automated workflow stops immediately. This prevents subsequent phases from running and ensures broken code does not pass quality gates.