verification-loop

To automate code quality checks before a PR, you can run a verification loop that executes builds, type checks, linting, test suites with coverage, and security scans, reporting a concise PR-ready health summary.

An end-to-end build verification workflow includes checking project builds with npm or pnpm, running TypeScript or Python type checks, executing lint, performing test suites with coverage, and scanning for security secrets.

You can run TypeScript type checks and linting through an automated verification loop that validates your code changes during feature completion or refactoring to catch issues early before integration.

Yes, the verification workflow supports both npm and pnpm build systems. It checks project builds with either package manager and surfaces recent logs to identify build failures.

To scan code changes for security secrets and common pitfalls, you run a security scan within the verification loop, which validates safety and correctness through diff reviews before PRs.

You should run a diff review during a refactoring session when completing a feature or preparing a PR. It validates the safety and correctness of your changes before they are integrated.