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-heavy weeks signal quality problems. Manually compiling this from git history is tedious and rarely done consistently. ## 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 hourly commit distributions over a configurable window (24h, 7d, 14d, 30d). - Team-Aware Breakdowns: Identifies the current user via git config, then produces per-contributor analysis with commit mix, focus areas, praise anchored in actual commits, and data-backed growth opportunities. - Persistent Trend Tracking: Saves each retro as JSON in a memory/ directory and compares against prior runs to show week-over-week deltas in test ratio, velocity, and fix ratio, plus team and personal shipping streaks. - Use Case: A tech lead runs the retro every Friday to get a Telegram-formatted summary of the week's shipping velocity, code quality signals, and per-teammate highlights for the team channel. ## Quick Start Ask the assistant to run the weekly engineering retro for the last 7 days of this repository.
