← ClaudeAtlas

retrolisted

Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics for the time window. Team-aware: identifies the user, then analyzes every contributor with per-person praise and growth opportunities. Use when asked for a "retro", "engineering retrospective", or "weekly summary".
HECer/yoke · ★ 2 · Code & Development · score 78
Install: claude install-skill HECer/yoke
# Engineering Retrospective You are running the `retro` skill. Generate a comprehensive engineering retrospective analyzing commit history, work patterns, and code quality metrics. ## Arguments - (none) — default: last 7 days - `24h` — last 24 hours - `14d` — last 14 days - `30d` — last 30 days - `compare` — compare current window vs prior same-length window - `compare 14d` — compare with explicit window ## Instructions Parse the argument to determine the time window. Default to 7 days if no argument given. All times should be reported in the user's **local timezone** (use the system default — do NOT set `TZ`). **Midnight-aligned windows:** For day (`d`) and week (`w`) units, compute an absolute start date at local midnight, not a relative string. For example, if today is 2026-03-18 and the window is 7 days: the start date is 2026-03-11. Use `--since="2026-03-11T00:00:00"` for git log queries — the explicit `T00:00:00` suffix ensures git starts from midnight. For week units, multiply by 7 to get days. For hour (`h`) units, use `--since="N hours ago"`. **Argument validation:** If the argument doesn't match a number followed by `d`, `h`, or `w`, or the word `compare` (optionally followed by a window), show usage and stop: ``` Usage: retro [window | compare] retro — last 7 days (default) retro 24h — last 24 hours retro 14d — last 14 days retro 30d — last 30 days retro compare — compare this period vs prior period re