Verification Loop Skill

Automating code quality checks before a pull request involves running a multi-phase verification loop that executes build, type checking, linting, test execution with coverage, and security scanning to ensure all changes pass rigorous quality assurance before code integration.

A multi-phase verification process for software development workflows systematically validates code changes by executing standard project build commands, type checking, linting, test execution with coverage, and security scans for secrets and debug statements before integration.

Running security scans for secrets and debug statements in your codebase is executed as part of a comprehensive code verification loop, which automatically checks for sensitive data and debugging artifacts alongside standard build, type, lint, and test executions.

This verification loop does not require specific external dependencies, but it requires execution of standard project build, type checking, linting, and test commands already configured within your software development environment to automate the multi-phase code verification process.

The best way to get a consolidated report on code quality and potential issues is to run an automated verification loop that generates a clear report summarizing the status of each verification phase, identifying specific issues to fix before submitting for review.

You should not use an automated code verification loop when your software development workflow does not require rigorous quality assurance before code integration, or if your project lacks standard build, type, lint, and test commands for the process to execute.