verification-loop

Topics in the source

• Verification Loop Skill
• When to Use
• Verification Phases
• Phase 1: Build Verification
• Phase 2: Type Check
• Phase 3: Lint Check
• Phase 4: Test Suite
• Phase 5: Security Scan

A comprehensive verification system for Claude Code sessions. 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 If build fails, STOP and fix before continuing. Report all type errors. Fix critical ones before continuing. Report: Total tests: X Passed: X Failed: X Coverage: X% Review each changed file for: Unintended changes Missing error handling Potential edge cases When the requested outcome requires deployment or target-environment verification, report target acceptance separately from local checks. Record the environment and installed version when known, the evidence, and the next permitted check or precise access dependency. Passing local checks, review, merge, or release does not establish target acceptance. Report VERIFIED or FAILED for an executed target check, with its evidence. Do not access production or make external changes without authorization. For local-only tasks, mark target acceptance as not applicable. For example: local checks PASS; staging verification NOT PERFORMED (no access); next step: an authorized maintainer runs the staging smoke test. After running

This is an excerpt. Refer to the complete source and its current requirements.