検証ループスキル

Code quality verification before a PR is automated by running sequential phases: build, type checking, linting, testing with coverage, and security scanning for secrets. This process executes project-specific commands to detect regressions and ensure code remains clean and secure.

An automated security scan for secrets and console logs inspects code diffs to identify hardcoded credentials and excessive debug statements. This prevents sensitive information leaks and debug clutter from passing pre-PR verification checks.

Linting and test coverage checks for a TypeScript project are executed by running project-specific lint and test commands. The verification process validates type safety, executes linters, and runs test suites while generating coverage reports to catch regressions.

Yes, the automated verification loop requires execution of project-specific build, lint, and test commands. It operates by running your custom commands to verify TypeScript type safety, execute linters, and run test suites with coverage reporting.

The best way to review code diffs and prevent regressions after refactoring is an automated verification loop. It executes multi-phase checks including build, type checking, testing, and security scanning, then displays code changes for manual inspection to ensure no regressions were introduced.