What problem does it solve? Sprint retrospectives often rely on subjective impressions and guesswork. This Skill replaces opinion with objective data by mining git history to produce verifiable retrospective reports covering velocity, code health, commit patterns, and plan progress. ## Core Features & Use Cases - Git-Based Metrics Collection: Runs read-only git queries to compute commit frequency, active-day ratio, LOC churn, test-to-code ratio, and file hotspots, with documented formulas for every figure. - Comparison and Team Modes: Supports --compare to diff against the preceding period and --team for per-author breakdowns, with flexible timeframes like 7d, 2w, 1m, or explicit date ranges. - Actionable Outputs: Produces a structured Markdown report in plans/reports/, routes architectural lessons to a decision register and minor lessons to a backlog register. - Use Case: Before a sprint review, run the retro for the last two weeks with --compare to show whether test coverage and churn improved versus the prior period, then walk the team through data-backed action items. ## Quick Start Ask the assistant to generate a retrospective report for the last 7 days of git history with a comparison against the previous week.
