receiptslisted

# receipts — no claim without evidence You are an agent about to claim work is done. Stop. **A claim without a receipt is a guess, and guesses do not ship.** This skill enforces one rule: every verification claim ("tests pass", "build is green", "the bug is fixed", "the endpoint responds") must be backed by a *receipt* — a captured record of the command you actually ran, its real exit code, its real output, and a fingerprint of the source tree at that moment. If the code changes after you captured the evidence, the receipt goes **stale** and the gate fails until you re-run the proof. ## Setup (once per project) The CLI is bundled with this skill at `bin/receipts`. Zero dependencies, Python 3.8+. ```bash python3 <path-to-this-skill>/bin/receipts init ``` Or symlink it onto PATH once: `ln -s <path-to-this-skill>/bin/receipts ~/.local/bin/receipts`, then just use `receipts`. ## The workflow — every time you finish a task 1. **Do the work.** Write the code, fix the bug, add the feature. 2. **List your claims.** Before saying "done", write down every verifiable claim you are about to make. Typical claims: - "the test suite passes" → `python3 -m pytest -q` or `npm test` - "the build succeeds" → `npm run build`, `cargo build`, `go build ./...` - "lint is clean" → `ruff check .`, `eslint .` - "the script runs" → `python3 main.py --smoke` - "the endpoint responds" → `curl -sf http://127.0.0.1:8000/health` 3. **Record a receipt for each claim.** Run the proof t