← ClaudeAtlas

prove-it-workslisted

Before saying a coding task is done, fixed, working or passing, run the project's real tests, build, typecheck and lint, show the real output, and inspect the change for the quiet ways "done" is not done (skipped or weakened tests, test commands that cannot fail, swallowed errors, hardcoded results, files outside the task, broken project rules, debug leftovers, secrets, dependency and migration mistakes). Use it at the end of every coding task, before committing or opening a PR, and whenever someone asks "did you test it?", "is it really done?" or "prove it". Also use it when the person corrects a mistake ("don't do that again") to turn the correction into a rule checked on every later proof.
shashwat14m/shipsnag-skills · ★ 0 · Code & Development · score 69
Install: claude install-skill shashwat14m/shipsnag-skills
# Prove It Works Before you say "done", prove it. This skill runs the project's real checks, shows their real output, and inspects your change for the problems that pass every check but still mean the work is not done. **The rule that matters:** never say a check passed unless you ran it in this turn and its output is in front of you. A check that did not run is NOT RUN, never PASS. The script's first line is the verdict; it goes first in your reply, word for word. ## Pick the mode | The situation | Mode | Run | |---|---|---| | You finished (or think you finished) a coding task, or someone asks whether it works | **Prove it** | `scripts/prove.py` | | The person corrected a mistake and it could happen again | **Never twice** | `scripts/rules.py add` | | You want to see which written project rules exist and how they are checked | List rules | `scripts/rules.py <repo>` | ## Prove it 1. Save the task you were given (the request plus any acceptance criteria) to a temporary file **outside the repo**, then run, with the Bash tool timeout set to 600000 ms (or in the background for longer suites): ```bash python3 <skill-dir>/scripts/prove.py <repo> --task-file <tmp-task-file> ``` - The change is worked out for you: on a feature branch, everything since the merge-base with the default branch (commits and uncommitted work); on the default branch, uncommitted work, or the last commit if it is from the last 24 hours. A merge commit or an old commit on a clean tree is "no change