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 digging through git history to answer these questions is tedious and rarely done consistently. ## Core Features & Use Cases - Commit and velocity analysis: Aggregates commits, PRs, insertions, deletions, test LOC ratio, and per-author leaderboards over configurable windows (24h, 7d, 14d, 30d). - Work pattern detection: Builds hourly commit histograms, detects coding sessions via a 45-minute gap threshold, and classifies deep, medium, and micro sessions. - Team-aware retrospectives: Identifies the current user via git config, then produces per-contributor breakdowns with praise and growth areas anchored in actual commits. - Persistent trend tracking: Saves JSON snapshots to a memory directory and computes deltas against prior retros, 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, hotspot files, focus score, and ship of the week, then compares it against last week's snapshot. ## Quick Start Ask the assistant to run the weekly engineering retro for the last 7 days of this repository.
