← ClaudeAtlas

receiptslisted

Generate a personal Claude Code usage & impact report ("receipts") from this machine's local session transcripts — for justifying Claude Code usage/spend to a manager, self-review, or "what have I been using this for" check-ins. Mines ~/.claude/projects locally (no extra API calls beyond one final write-up), cross-references local git history, and writes a markdown report plus a self-contained HTML receipt to your home directory. Use when the user asks for "receipts", an "impact report", "usage report", wants to "show my Claude Code activity", "prove the value of Claude Code", or runs `/receipts`.
thevibeworks/claude-code-docs · ★ 21 · AI & Automation · score 74
Install: claude install-skill thevibeworks/claude-code-docs
# /receipts — personal Claude Code impact report Generates a markdown report of one developer's own Claude Code activity, built entirely from local data: - **Source data**: this machine's session transcripts at `~/.claude/projects/**/*.jsonl` (every session, every project, already on disk — nothing to set up). - **Cost**: the mining step is a local Node script — file I/O + regex, zero API calls. The only model call is one final write-up over a small (~10-20KB) JSON summary, regardless of how much history was scanned. - **Cross-reference**: local `git log` per repo (no network) to sanity-check commit activity against CC session activity. ## Step 1 — figure out the period Parse `$ARGUMENTS`: - "week" → 7, "month" → 30 (default if nothing given), "quarter" → 90, "year" → 365 - a bare number → that many days - a project name/substring (e.g. "for anthropic") → pass through as `--repo <substr>`. It matches against the resolved project name, case-insensitively, and scopes the entire report — totals included — to matching projects. ## Step 2 — run the miner The script `mine-transcripts.mjs` ships alongside this SKILL.md, under `scripts/`. Use its absolute path: ```bash node <skill-dir>/scripts/mine-transcripts.mjs --days <N> [--repo <substr>] --html /tmp/cc-receipt.html ``` Use that fixed temp path — the real `since`/`until` are computed by the script and only known once it has run, so don't try to put them in this filename. Steps 4 and 5 name the final files, by