What problem does it solve? Developers often open merge requests with unmet requirements, tautological tests that cannot fail, stale documentation claims, and unverified gate results, causing expensive review rounds and re-ratifications. This Skill runs an author-side completeness pass so a merge request arrives carrying evidence rather than claims. ## Core Features & Use Cases - Requirement and DoD Verification: Enumerates every Issue requirement and Definition of Done item, marking each met or unmet with real command output as evidence. - Mutation Testing Discipline: Instructs authors to mutate source code and confirm every new assertion can actually fail, catching tautological tests that coverage cannot see. - Drift and Production-Risk Sweeps: Greps the repository for claims the change made false, tries alternative spellings for anything parsed, and checks production-risk axes like dependencies, secrets, and deploy paths. - Use Case: Before opening a pull request on a hook or pipeline change, run this pass to catch a flag spelling bug, seven non-failing assertions, and stale README counts in minutes instead of across eight corrective commits. ## Quick Start Ask the agent to run the code-review completeness pass on your finished slice before opening the merge request.
