Verification Loop Skill

To automate code quality checks before a pull request, run a multi-phase verification process that validates build success, type correctness, linting, test coverage, and security vulnerabilities to ensure all quality gates are met.

A comprehensive pre-commit verification loop includes build validation, type checking, code style adherence, test suite execution with coverage, security scans for secrets and console logs, and code diff analysis.

Yes, you can run security scans and linting together during continuous development using a continuous mode, which offers guidance for running verification checks periodically throughout long development sessions.

Yes, the verification process detects security vulnerabilities including exposed secrets and console logs by analyzing code diffs before commits to ensure quality gates are met and prevent vulnerabilities.

The best way to ensure type correctness and build success before committing is executing a multi-phase verification process that validates builds, checks types, and provides a clear pass or fail status report.

You need a multi-phase verification process because testing alone misses build failures, type errors, linting violations, and security vulnerabilities, which this process catches before pull requests to reduce bug risks.