helplisted

# gitreceipts plugin — help Present this reference to the user, concisely and formatted: **What it is.** gitreceipts reads a Claude Code session against the repo's git history: each prompt you typed → the work it drove → the commit it became. Runs locally; nothing leaves the machine. **Setup.** Needs the `git-receipts` binary (0.1.1+, identity needs 0.1.3 — the skills offer the upgrade if yours is older, and work either way). If it's missing, the skills detect what you have and offer to install it — your approval, your choice of route: `brew install cloudcraft-ai/tap/gitreceipts` · `cargo install gitreceipts` (then `git-receipts man --install` once) · or a checksum-verified prebuilt binary, no package manager needed. **Two skills, one receipt.** | | | |---|---| | **`/gitreceipts:recap`** | *where are things* — the state-face: what you asked, what the agent did, what landed. Fires on "what happened here", "catch me up", "recap that commit". | | **`/gitreceipts:audit`** | *where should I look* — the attention-ladder: every claimed edit checked against the real commit blobs, and the broken-promise count. Fires on "did that land", "any broken promises", and when a delegated lane reports done. | Same receipt and the same checking underneath — recap just doesn't lead with the score. Recap orients; the audit escalates. **Say it however you like** — both skills map plain language to scopes: | You say | It runs | |---|---| | nothing / "what happened" | all sessions for this re