What problem does it solve? Engineering teams lack visibility into how work actually happened over a week or sprint — who shipped what, when deep work occurred, whether test coverage kept pace, and how output trends over time. Manually assembling this from git history is tedious and rarely done consistently. ## Core Features & Use Cases - Commit and code metrics: Aggregates commits, insertions, deletions, test LOC ratio, PR size distribution, and file churn hotspots from git history over configurable windows (24h, 7d, 14d, 30d). - Team-aware analysis: Identifies the current user via git config, then breaks down per-contributor commits, focus areas, session patterns, and test discipline with specific praise and growth suggestions. - Work pattern detection: Builds hourly commit histograms, detects coding sessions using a 45-minute gap threshold, tracks shipping streaks, and computes focus scores. - Persistent history and trends: Saves retro snapshots to .context/retros/ and compares against prior runs, plus a compare mode for period-over-period deltas and a global mode across projects. - Use Case: At the end of a sprint, run /retro 14d to get a full report: a per-person leaderboard, week-over-week test ratio trends, the biggest ship of the period, and concrete growth feedback for each teammate. ## Quick Start Ask the assistant to run a weekly engineering retrospective over the last 7 days of git history with per-contributor breakdowns and trend comparison.
