verification-loop

name	verification-loop
description	A comprehensive verification system for Claude Code sessions.
model	gpt-5.4
model_reasoning_effort	medium
sandbox_mode	workspace-write

Verification Loop verification routine

A comprehensive verification system for Claude Code sessions.

When to Use

Invoke this skill:

• After completing a feature or significant code change
• Before creating a PR
• When you want to ensure quality gates pass
• After refactoring

Verification Phases

Phase 1: Build Verification

npm run build 2>&1 | tail -20

If build fails, STOP and fix before continuing.

Phase 2: Type Check

npx tsc --noEmit 2>&1 | head -30

Report all type errors. Fix critical ones before continuing.

Phase 3: Lint Check

npm run lint 2>&1 | head -30

Phase 4: Test Suite

npm run test -- --coverage 2>&1 | tail -50

Report:

• Total tests: X
• Passed: X
• Failed: X
• Coverage: X%

Phase 5: Security Scan

grep -rn "sk-" --include="*.ts" --include="*.js" . 2>/dev/null | head -10
grep -rn "api_key" --include="*.ts" --include="*.js" . 2>/dev/null | head -10

Phase 6: Diff Review

git diff --stat
git diff HEAD~1 --name-only

Review each changed file for:

• Unintended changes
• Missing error handling
• Potential edge cases

Output Format

After running all phases, produce a verification report:

VERIFICATION REPORT
==================

Build:     [PASS/FAIL]
Types:     [PASS/FAIL] (X errors)
Lint:      [PASS/FAIL] (X warnings)
Tests:     [PASS/FAIL] (X/Y passed, Z% coverage)
Security:  [PASS/FAIL] (X issues)
Diff:      [X files changed]

Overall:   [READY/NOT READY] for PR

Continuous Mode

For long sessions, run verification every 15 minutes or after major changes.

Run: /verify

Integration with Hooks

This skill complements PostToolUse hooks but provides deeper verification. Hooks catch issues immediately; this skill provides comprehensive review.