verification-loop

Code verification before merging is initiated by running the /verify command, which executes a comprehensive quality gate process covering build integrity, type checking, linting, testing, and security checks.

Continuous quality verification maintains code standards throughout a development workflow by systematically checking build integrity, types, linting, and security. It integrates with PostToolUse hooks to detect issues in real-time during Claude Code sessions.

Yes, running comprehensive code quality checks requires command-line tools including npm, python, git, and grep. These dependencies are necessary to execute the build, testing, and diff review operations during the verification process.

Yes, you can integrate security checks and linting into continuous integration by running a verification loop that validates code at multiple levels. The process complements PostToolUse hooks for real-time issue detection during development.

The best way to review diffs and detect vulnerabilities is using a comprehensive verification process that systematically checks build integrity, security, and adherence to best practices, providing a deeper review than standard real-time hooks.

A verification loop fails during type checking and linting when the code violates type constraints or linting rules. The process rigorously validates these quality gates alongside build integrity and security checks before allowing changes.