verification-loop

Execute automated build, type, lint, test, security, and diff checks on Claude Code sessions.

1|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/samChang72/custom-skills --skill verification-loop-samchang72
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/samChang72/custom-skills/tree/main/claude-config/skills/verification-loop
Command: npx skills add https://github.com/samChang72/custom-skills --skill verification-loop-samchang72

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a comprehensive verification system for Claude Code sessions, ensuring that quality gates are passed and code changes meet the required standards.

Core Features & Use Cases

  • Verification Phases: Automates a series of verification phases, including build, type check, lint check, test suite, security scan, and diff review.
  • Continuous Mode: Allows for ongoing verification every 15 minutes or after significant changes, maintaining a high level of code quality throughout a session.
  • Integration with Hooks: Complements PostToolUse hooks with deeper verification capabilities, providing immediate issue detection and comprehensive review.

Quick Start

Run the verification process by typing /verify within a Claude Code session.

Frequently Asked Questions about verification-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code review and quality checks for Claude Code sessions?

Automated code verification for Claude Code sessions executes build checks, type checking, linting, testing, security scanning, and diff review sequentially to ensure changes meet quality standards before a Pull Request.

What is continuous verification and how does it maintain code quality during development?

Continuous verification runs automated quality gates every 15 minutes or after significant code changes, maintaining ongoing code quality throughout a Claude Code session by detecting issues immediately.

How do I run build verification, linting, and security scans before creating a Pull Request?

Run automated verification phases including build, type check, lint, test suite, and security scan by typing /verify within a Claude Code session to ensure Pull Request readiness.

Do I need Python to run automated code verification scripts in Claude Code?

Yes, Python is required to execute the verification scripts that automate build checks, type checking, linting, testing, security scanning, and diff review in Claude Code sessions.

Does automated code verification work with PostToolUse hooks for issue detection?

Automated code verification complements PostToolUse hooks by providing deeper verification capabilities, combining immediate issue detection from hooks with comprehensive quality gate reviews.

What are the limitations of relying on automated verification phases for code readiness?

Automated verification phases check build, types, lint, tests, security, and diffs, but continuous mode runs only every 15 minutes or after significant changes, meaning very recent minor edits might delay verification.