Weekly Engineering Retrospective

--- name: gstack-openclaw-retro description: "Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware with per-person contributions, praise, and growth areas. Use when asked for weekly retro, what shipped this week, or engineering retrospective." --- # Weekly Engineering Retrospective Generates a comprehensive engineering retrospective analyzing commit history, work patterns, and code quality metrics. Team-aware: identifies the user running the command, then analyzes every contributor with per-person praise and growth opportunities. ## Arguments - 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 ## Instructions Parse the argument to determine the time window. Default to 7 days. All times should be reported in the user's local timezone. Midnight-aligned windows: For day units, compute an absolute start date at local midnight. 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. For hour units, use --since="N hours ago". --- ### Step 1: Gather Raw Data First, fetch origin and identify the current user: ``bash git fetch origin main --quiet git config user.name git config user.email ` The name returned by git config user.name is **"you"** ... the person reading this retro. All other authors are teammates. Run ALL of these git commands (they are independent): `bash # All commits with timestamps, subject, hash, author, files changed git log origin/main --since="<window>" --format="%H|%aN|%ae|%ai|%s" --shortstat # Per-commit test vs total LOC breakdown with author git log origin/main --since="<window>" --format="COMMIT:%H|%aN" --numstat # Commit timestamps for session detection and hourly distribution git log origin/main --since="<window>" --format="%at|%aN|%ai|%s" | sort -n # Files most frequently changed (hotspot analysis) git log origin/main --since="<window>" --format="" --name-only | grep -v '^$' | sort | uniq -c | sort -rn # PR numbers from commit messages git log origin/main --since="<window>" --format="%s" | grep -oE '[#!][0-9]+' | sort -t'#' -k1 | uniq # Per-author file hotspots git log origin/main --since="<window>" --format="AUTHOR:%aN" --name-only # Per-author commit counts git shortlog origin/main --since="<window>" -sn --no-merges # Test file count find . -name '*.test.*' -o -name '*.spec.*' -o -name '*_test.*' -o -name '*_spec.*' 2>/dev/null | grep -v node_modules | wc -l # Test files changed in window git log origin/main --since="<window>" --format="" --name-only | grep -E '\.(test|spec)\.' | sort -u | wc -l ` --- ### Step 2: Compute Metrics Calculate and present these metrics in a summary: - **Commits to main:** N - **Contributors:** N - **PRs merged:** N - **Total insertions:** N - **Total deletions:** N - **Net LOC added:** N - **Test LOC (insertions):** N - **Test LOC ratio:** N% - **Version range:** vX.Y.Z → vX.Y.Z - **Active days:** N - **Detected sessions:** N - **Avg LOC/session-hour:** N Then show a **per-author leaderboard** immediately below: ` Contributor Commits +/- Top area You (garry) 32 +2400/-300 browse/ alice 12 +800/-150 app/services/ bob 3 +120/-40 tests/ ` Sort by commits descending. The current user always appears first, labeled "You (name)". --- ### Step 3: Commit Time Distribution Show hourly histogram in local time: ` Hour Commits ████████████████ 00: 4 ████ 07: 5 █████ ... ` Identify: - Peak hours - Dead zones - Bimodal pattern (morning/evening) vs continuous - Late-night coding clusters (after 10pm) --- ### Step 4: Work Session Detection Detect sessions using **45-minute gap** threshold between consecutive commits. Classify sessions: - **Deep sessions** (50+ min) - **Medium sessions** (20-50 min) - **Micro sessions** (<20 min, single-commit) Calculate: - Total active coding time - Average session length - LOC per hour of active time --- ### Step 5: Commit Type Breakdown Categorize by conventional commit prefix (feat/fix/refactor/test/chore/docs). Show as percentage bar: ` feat: 20 (40%) ████████████████████ fix: 27 (54%) ███████████████████████████ refactor: 2 ( 4%) ██ `` Flag if fix ratio exceeds 50% ... signals a "ship fast, fix fast" pattern that may indicate review gaps. --- ### Step 6: Hotspot Analysis Show top 10 most-changed files. Flag: - Files changed 5+ times (churn hotspots) - Test files vs production files in the hotspot list - VERSION/CHANGELOG frequency --- ### Step 7: PR Size Distribution Estimate PR sizes and bucket them: - Small (<100 LOC) - Medium (100-500 LOC) - Large (500-1500 LOC) - XL (1500+ LOC) --- ### Step 8: Focus Score + Ship of the We