What problem does it solve? Engineering teams and solo developers lack visibility into their own work patterns: when they code, how much they ship, test coverage discipline, and whether velocity is improving week over week. Manually digging through git history to answer these questions is tedious and rarely done consistently. ## Core Features & Use Cases - Commit and session analysis: Parses git log to compute commits, LOC, test ratios, PR sizes, hotspot files, and detects work sessions using a 45-minute gap threshold. - Team-aware breakdowns: Identifies the current user via git config and produces per-contributor sections with specific praise and growth suggestions anchored in actual commits. - Persistent trend tracking: Saves JSON snapshots to .context/retros/ and compares against prior runs to show week-over-week deltas in velocity, test ratio, and session depth. - Use Case: A tech lead runs /retro every Friday to get a data-backed summary of the team's week, including shipping streaks, focus scores, and the highest-impact PR, ready to share in a team sync. ## Quick Start Type /retro to analyze the last 7 days of commits, or /retro compare 14d to compare this period against the prior one.
