What problem does it solve? Engineering teams lack visibility into what actually shipped each week, how work patterns evolve, and where code quality is drifting. This Skill automates the weekly retrospective by mining git history, session data, and prior retro records into a structured report. ## Core Features & Use Cases - Commit and velocity analysis: Breaks down commits, LOC, PR sizes, fix chains, and shipping streaks across the team. - Team-aware breakdowns: Per-person contributions with praise and growth areas anchored in actual commits, plus AI-assisted commit percentages. - Trend tracking: Compares against prior retros stored in .context/retros/*.json to surface week-over-week changes in test health, focus, and plan completion. - Use Case: At the end of a sprint, ask for a weekly retro and receive a report covering shipping velocity, test health deltas, shortcut debt, top team wins, and three habits for next week. ## Quick Start Ask the assistant to run a weekly retro for this repository to generate the full engineering retrospective report.