What problem does it solve? Engineering teams lack visibility into what actually shipped each week, how work is distributed across contributors, and whether code quality patterns like fix-heavy commits or churn hotspots signal deeper problems. This Skill turns raw git history into a structured retrospective report. ## Core Features & Use Cases - Commit and Metrics Analysis: Aggregates commits, PRs, insertions/deletions, test LOC ratio, active days, and session detection from git history over configurable windows (24h, 7d, 14d, 30d). - Team-Aware Breakdown: Identifies the current user via git config and produces a per-author leaderboard with praise and growth areas for each contributor. - Pattern Detection: Surfaces commit time distributions, work session classification, commit type breakdowns, hotspot files, and PR size buckets, flagging signals like fix ratios above 50%. - Use Case: At the end of a sprint, run the retro to get a report showing who shipped what, which files churned most, whether test coverage kept pace, and how this period compares to the prior one. ## Quick Start Ask the assistant to run a weekly retro analyzing the last 7 days of commits on the main branch.
