What problem does it solve? AI agents and developers often claim work is done, fixed, or passing based on stale output, prior-session results, or confidence rather than fresh evidence. This Skill enforces a verification gate so no completion claim is made without running the proving command after the final edit and reading its output. ## Core Features & Use Cases - Evidence Gate: Blocks completion claims until the proving command or check has run after the final relevant edit and its output, exit code, and failure count have been read. - Claim-to-Evidence Mapping: Defines required evidence for common claims such as tests passing, lint being clean, builds succeeding, bugs being fixed, and PRs being ready. - Red Flag Detection: Flags risky wording like "done", "fixed", "passes", "ready", and "safe to merge" as triggers to stop and verify before committing, pushing, or opening a PR. - Use Case: Before handing a bug fix back to a reviewer, run the regression test, confirm it passes, and report the exact command and result instead of stating the fix "should work". ## Quick Start Before claiming this task is complete, run the relevant test or build command and report the actual output as evidence.