What problem does it solve? Engineering teams lack visibility into how they actually work: who shipped what, when coding happens, whether test coverage is improving, and whether fix-to-feature ratios signal quality problems. Manually compiling this from git history every week is tedious and inconsistent. ## Core Features & Use Cases - Automated Git Analysis: Runs a battery of git log commands to compute commits, LOC, test ratios, PR sizes, hotspots, session patterns, and commit-type breakdowns over configurable windows (24h, 7d, 14d, 30d). - Team-Aware Reporting: Identifies the current user via git config, then produces per-contributor analysis with praise and growth areas anchored in actual commits, plus streak tracking and focus scores. - Persistent Trend Tracking: Saves JSON snapshots to a memory/ directory and compares against prior retros to show week-over-week deltas in test ratio, velocity, and fix ratio. - Use Case: A team lead asks "what shipped this week?" and receives a Telegram-formatted retro with a tweetable summary, per-person breakdowns, top wins, and three actionable improvements. ## Quick Start Ask the agent to run a weekly engineering retrospective for the last 7 days of this repository.
