verify
Installation
SKILL.md
Verify
A proof gives every claim the work makes evidence that a skeptical reviewer can rerun, and that would have come out differently had the work been wrong. Passing tests alone are not a proof: a check counts only when it observes the behavior and has been shown able to fail.
Verify observes; it does not fix. When a claim fails, record it and report it, leaving production code as it is.
Copy this checklist and track progress:
- [ ] 1. Claims listed
- [ ] 2. Evidence gathered
- [ ] 3. Every check shown able to fail
- [ ] 4. Regressions checked
- [ ] 5. Proof written
- [ ] 6. Proof reproduced
- [ ] 7. Cleaned up and reported