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 d
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.
| 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> |
python3 <skill-dir>/scripts/prove.py <repo> --task-file <tmp-task-file>
--base <ref> overrides this.--timeout seconds (default 300); all commands together get --budget seconds (default 540), after which the rest are NOT RUN. If the Bash tool would stop the script sooner, the script's children are stopped with it, so raise the Bash timeout instead of lowering these.| Verdict | Means | You say |
|---|---|---|
| PROVEN: ... | A task was given, every check ran and passed, no problems in the change | Done, with the proof and your requirements list (step 4) |
| CHECKS PASS (...) | Nothing failed, but something was not covered: no task, no test command, nothing to inspect, or a check that fails only on untouched lines | The checks pass, and exactly what the line says was not covered |
| NOT VERIFIED: ... | Checks could not run (dependencies, tools, time budget, unsafe to run) | It is not proven; name the command that would let them run, and ask once |
| NOT DONE: ... | A check fails or the change has a problem | "Not done yet", then each item |
.only, add @ts-ignore / # type: ignore / eslint-disable, catch and ignore the error, special-case the test input, stub out the code under test, lower a coverage threshold, add || true, or switch off a CI job. The script flags all of these.references/review-checklist.md, even when the verdict is PROVEN. The scripts match names and patterns; they cannot tell whether the change does what the task meant.file:line in the diff that delivers it, or MISSING. Docs, comments, usage strings and your own summary are not evidence. Any MISSING row means not done, whatever the first line says.When the person corrects a mistake that a pattern, a path or a command could catch next time, offer to add a rule, then run:
python3 <skill-dir>/scripts/rules.py add --repo <repo> --kind grep --pattern '<regex>' --why '<the mistake, in one line>' [--glob 'src/**']
python3 <skill-dir>/scripts/rules.py add --repo <repo> --kind forbid-path --pattern 'src/generated/' --why '<why it must not change>'
python3 <skill-dir>/scripts/rules.py add --repo <repo> --kind require-cmd --pattern 'npm run e2e' --why '<why it must pass>'
grep: the regex must not appear in lines a change adds (optionally only in files matching --glob).forbid-path: files matching the glob or folder must not be added, edited or deleted.require-cmd: the command must pass. Only check-like commands are accepted (no installs, deletes, git writes, network or redirects).Show the person the rule as written and the dry run. Rules live in <repo>/.shipsnag/rules.md, run on every later proof, and can be edited or deleted by hand. Mention the file the first time.
--only, the "Not covered" line, and "What this can't see" when it applies.Add --ledger to append one line to <repo>/.shipsnag/ledger.md: date, verdict, check counts and cause numbers, never code or secrets. Use it unless the person doesn't want files added; mention the file the first time.
scripts/prove.py: detects and runs the project's commands (package.json scripts with the package manager from packageManager or the lockfile; Makefile targets; pyproject task tables; pytest or unittest; ruff, flake8, mypy; cargo; go; Maven, Gradle, Bundler, Composer, .NET, Deno; documented and conventional commands) with a timeout, a total budget and an offline environment. Commands named or doing deploy, release, publish, migrate, install or network work are never run automatically. --json for machine output (with a coverage block); exit codes 0 PROVEN, 1 NOT DONE, 3 CHECKS PASS or NOT VERIFIED, 2 tool error. --hook is the optional Claude Code Stop hook (see README).scripts/diffcheck.py and scripts/fakes.py: the change inspection (causes 5-17), including test commands and CI jobs that cannot fail, tests that cannot fail, swallowed exceptions, special-cased inputs, hardcoded results, rewritten golden files, lowered coverage, lockfiles not updated, schema changes without migrations and conflict markers. Minified, generated and vendored files are skipped by the line checks. scripts/rules.py: project rules from CLAUDE.md, AGENTS.md, .cursorrules, .cursor/rules, .github/copilot-instructions.md, CONTRIBUTING.md, .windsurfrules and .shipsnag/rules.md.references/review-checklist.md: your review pass, how to read tests, how to judge each "check these" item, and what to say instead of "done"..shipsnag/; the project's own commands may write their usual outputs, and the change is read before any command runs.Weekly roundup of top Claude Code skills, MCP servers, and AI coding tips.