auditlisted

# git receipts — the verdict **recap answers "where are things". audit answers "where should I look".** This is the attention-ladder, and the word is close to literal: the four-dot verdict IS the ladder, and every switch below is a rung on it. The audit answers one question: **did every claimed edit actually land?** It reconciles the session log's file claims against the real commit blobs and reports what balanced, what didn't, and what nothing explains. For "where are things", use `/gitreceipts:recap` — same receipt, same checking, read as a state-face. This skill is for when the number matters. ## Prerequisite: the binary ```bash command -v git-receipts >/dev/null && git-receipts --version || echo MISSING ``` If MISSING, offer the install (never unasked, never a refusal) — the routes and the checksum-verified fallback are in `/gitreceipts:recap`, which owns that flow. Version floor for the views below: **0.1.1**. ## Running it ```bash git receipts audit --summary --emoji --no-pager --color never ``` That's the condensed verdict: the headline, then one row per commit — `commit · subject · claims · findings`. Emoji because chat strips terminal color, and the dots ARE the color layer here: - 🟢 **green** — nothing to report - ⚪ **grey** — explained findings: a file written and discarded before any commit, a failed command, an errored MCP call. Each carries its reason. - 🟡 **amber** — **un**explained residue: git recorded a change no claim and no command accounts