Verification Loop Skill

Automating code quality checks before a pull request involves running builds, type checking, linting, tests, and security scans in a single verification loop to enforce quality gates and prepare code for integration.

A multi-phase verification process systematically executes build, type, lint, test, and security scans with coverage analysis and diff review to ensure code changes meet project standards before integration or release.

Security scanning for vulnerabilities and console logs is executed as part of an automated verification loop, identifying hidden secrets and debugging artifacts to reduce security risks before code integration.

The automated verification loop operates without external dependencies, relying on internal scripts to run build, type checking, linting, test execution, and security scanning processes directly on the current codebase.

The best way to review code diffs and enforce quality gates is using an automated verification skill that provides a structured diff review alongside comprehensive test execution and coverage analysis.

Running linting and test coverage analysis before merging code ensures that linting rules are followed and tests are robust, significantly improving overall code quality and reducing the likelihood of introducing bugs.