What problem does it solve? Engineering teams lack visibility into how they actually work — who shipped what, when deep work happens, whether test coverage is improving, and how this week compares to last. This Skill automates the weekly retrospective by mining git history and turning raw commits into actionable team insights. ## Core Features & Use Cases - Commit & Metrics Analysis: Aggregates commits, PRs, insertions/deletions, test LOC ratio, and fix-vs-feature breakdown over configurable windows (24h, 7d, 14d, 30d). - Team-Aware Breakdown: Identifies each contributor, computes per-person focus areas, session patterns, and test discipline, then generates specific praise and growth suggestions anchored in real commits. - Work Pattern Detection: Builds hourly commit histograms, detects deep/medium/micro coding sessions via 45-minute gap analysis, and tracks consecutive-day shipping streaks. - Persistent Trend Tracking: Saves JSON snapshots to .context/retros/ and compares against prior retros to show week-over-week deltas in test ratio, velocity, and fix rate. - Use Case: At the end of a sprint, run the retro to get a leaderboard of contributions, a ship-of-the-week highlight, hotspot files with high churn, and a trends table showing whether code quality is improving. ## Quick Start Ask the assistant to run a weekly engineering retrospective over the last 7 days of this repository's commit history.
