verification-loop

PR readiness verification automates end-to-end project checks by running builds, type checks, linting, tests, and security scans. This process enforces Quality Gates and generates a comprehensive report to reduce regression risks before merging.

TypeScript type checking and Python linting are handled by executing npx tsc --noEmit and ruff check respectively. The verification workflow applies these checks automatically alongside builds and tests to ensure PR readiness.

You can enforce an 80% test coverage threshold in your CI workflow. The verification process executes tests with coverage and specifically targets a minimum coverage of 80% to ensure code quality before PR submission.

Automated security scanning does check for hardcoded secrets and console logs. It identifies potential security risks like API keys and debug statements to ensure sensitive data is not exposed in the changelist before PR readiness.

Reviewing changelist diffs during refactoring is best handled by an automated verification report. It displays changed content and file change lists, highlighting potential issues introduced during feature work or refactoring to ensure PR readiness.

Multi-language repository verification is supported for npm and pnpm projects. The process handles build validation across these package managers and applies appropriate type checking and linting for both TypeScript and Python codebases.