verification-loop

Automating code verification involves running build, type, lint, test, and security checks to maintain standards. This process systematically executes these checks to ensure code quality and security before creating pull requests.

Continuous code quality checks can be run using a continuous mode that executes verification at regular intervals. This complements PostToolUse hooks to provide a deeper verification process throughout the software development lifecycle.

Yes, npm and tsc are required dependencies for running automated type and lint checks. The verification process specifically relies on npm, pnpm, tsc, pyright, and grep to execute its build, type, and lint verification stages.

Yes, you can use a verification loop to review codebase diffs before a pull request. After completing a feature or significant code change, it ensures all quality gates pass by reviewing the changes made to the codebase.

The automated security scan checks for potential security vulnerabilities within the codebase. It functions as part of a comprehensive verification suite that also includes build validation, type checking, linting, and test coverage execution.

Code verification can fail when lint and test scripts pass if the build process, type checking via tsc or pyright, or the security scan detects errors. The verification loop aggregates results across all these distinct quality gates.