What problem does it solve? Engineering teams and solo developers lack visibility into their actual work patterns—commit velocity, test discipline, session habits, and code churn—making it hard to run data-driven retrospectives without manual git archaeology. ## Core Features & Use Cases - Commit & Velocity Analysis: Aggregates commits, PRs, insertions/deletions, test LOC ratio, and commit-type breakdown (feat/fix/refactor) from origin/main over configurable windows (24h, 7d, 14d, 30d). - Team-Aware Breakdown: Identifies the current user via git config, then produces per-contributor leaderboards with specific praise and growth suggestions anchored in real commits. - Session & Streak Detection: Detects coding sessions using a 45-minute gap threshold, tracks consecutive-day shipping streaks, and charts hourly commit distribution in Pacific time. - Persistent Trend Tracking: Saves JSON snapshots to .context/retros/ and compares current metrics against prior retros, plus a compare mode for window-over-window deltas. - Use Case: A tech lead runs /retro 14d every Friday to get a per-person summary of the sprint—who shipped what, test coverage trends, and three concrete habits to adopt next week. ## Quick Start Run /retro to generate a retrospective of the last 7 days of commits on origin/main, or /retro compare 14d to compare this period against the prior one.
