Enforces rigorous evidence-based verification before any task is marked as finished, committed, or merged.
This skill implements an 'Iron Law' for development within Claude Code, preventing premature completion claims by requiring fresh, objective verification evidence. It acts as a mandatory gate function, requiring the execution of test commands, builds, or linters and the meticulous analysis of their outputs before any success statement can be made. By eliminating rationalizations and 'should work' assumptions, it ensures high code quality, builds developer trust, and prevents regression errors in complex software environments.
Key Features
01Systematic verification patterns for tests, builds, and linting processes
02Independent verification protocols for agent-delegated tasks and VCS diffs
03Mandatory gate function for all completion and success claims
04TDD Red-Green cycle validation for robust regression testing
051 GitHub stars
06Detection and prevention of speculative language like 'should' or 'probably'
Use Cases
01Confirming all project requirements are met using a line-by-line checklist verification
02Validating code changes rigorously before committing or opening Pull Requests
03Ensuring bug fixes are verified against original failing symptoms via automated tests
