What problem does it solve? Engineering teams lack visibility into what actually shipped each week, how work patterns affect code quality, and whether metrics like test ratio and fix ratio are improving over time. Manually digging through git history to build a retrospective is tedious and rarely produces consistent, comparable data. ## Core Features & Use Cases - Automated Git Analysis: Runs a battery of git log queries to compute commits, LOC, test ratios, PR sizes, hotspots, session patterns, and commit-type breakdowns over 24h, 7d, 14d, or 30d windows. - Team-Aware Reporting: Identifies the current user via git config, then produces per-contributor analysis with praise and growth opportunities anchored in actual commits. - Persistent Trend Tracking: Saves each retro as JSON in memory/ and compares against prior runs to show week-over-week deltas, plus team and personal shipping streaks. - Use Case: A tech lead asks "what shipped this week?" every Friday and receives a Telegram-formatted retro with a tweetable summary, focus score, ship of the week, and three actionable improvements. ## Quick Start Ask the assistant to run the weekly engineering retro for the last 7 days of this repository.
