What problem does it solve? Developers who use Claude Code often struggle to explain or justify their usage and spend to managers, or to answer "what have I actually been using this for?" This Skill mines local session transcripts and git history to produce a concrete, evidence-based impact report without manual data gathering. ## Core Features & Use Cases - Local transcript mining: A Node script scans ~/.claude/projects session logs offline, aggregating sessions, prompts, active days, files touched, and per-project spend share with zero extra API calls. - Git cross-referencing: Correlates Claude Code activity with local git history to count commits that actually carry Claude-assisted work, avoiding inflated or misleading numbers. - Dual output: Produces a markdown report for pasting into docs plus a self-contained HTML receipt with an Export CSV button, saved to your home directory. - Use Case: Before a performance review, run the report for the last quarter to show your manager which projects consumed Claude Code time, what shipped, and how many PRs were opened. ## Quick Start Ask Claude to run /receipts for the past month to generate your Claude Code impact report.