This skill acts as a critical quality gate for Claude, preventing premature or dishonest completion claims by requiring fresh, verifiable evidence for every status update. It mandates a systematic 'Gate Function' workflow: identifying the proof, executing the command, reading the output, and only then asserting success. By eliminating guesswork and 'should-be-fixed' assumptions, it ensures that commits, pull requests, and status reports are backed by actual test passes, successful builds, and clean linting results, ultimately building higher trust and reducing technical debt in the development lifecycle.
Key Features
01Red-green cycle validation for reliable regression testing
02Strict 'Iron Law' requiring fresh command output before any status claims
03Comprehensive verification checklists for builds, tests, and requirements
04Anti-rationalization framework to prevent 'should work' assumptions
05Systematic Gate Function workflow for consistent verification steps
060 GitHub stars
