← ClaudeAtlas

prove-fixlisted

Prove that the tests for a code change would have caught the bug, by running every added or edited test with the change and with the old code (red/green check). Use this after fixing a bug, changing behavior or refactoring with tests added or edited, before saying the work is done, and whenever the user asks whether tests really cover a fix, whether a test is meaningful, or to verify a PR's tests. Works with pytest, vitest and jest in a git repository. Reports PROVEN, GUARD, THEATER, WEAK, BROKEN, FLAKY, PRESERVED or CHANGED per test.
syntaxixr/receipts · ★ 1 · Testing & QA · score 72
Install: claude install-skill syntaxixr/receipts
# Prove the fix before calling it done A green test suite only says the tests pass. It does not say they would have caught the bug. Receipts runs every test you added or edited twice: once with your change, and once with the changed source files reverted to the base branch. A test for a fix must fail on the old code and pass on the new one. Otherwise it proves nothing about your change, however green it is. ## Run it From the repository root: ```bash node <skill-dir>/scripts/cli.js check ``` `<skill-dir>` is the directory this SKILL.md is in: Claude Code shows it as the skill's base directory, and inside the Claude Code plugin it is `${CLAUDE_PLUGIN_ROOT}/skills/prove-fix`. The CLI is bundled there and has no dependencies. If the scripts folder is missing, run `npx -y github:syntaxixr/receipts check` instead. Receipts compares against the PR base, `origin/HEAD`, `main` or `master`; pass `--base <ref>` for anything else. It checks committed and uncommitted work alike. The red run edits files in place and restores every byte afterwards; if it was killed hard, `check` refuses to start until you run `restore`. ## Workflow for a bug fix 1. Write the test that reproduces the bug first, and run it: it should fail. 2. Make the fix. 3. Run Receipts and act on each verdict: | Verdict | Meaning | What to do | |---|---|---| | PROVEN | Fails without the change, passes with it | Done | | GUARD | Passes on both sides, next to a PROVEN test | Fine: it guards the neighboring behavior