← ClaudeAtlas

retrolisted

Weekly engineering retrospective with persistent metrics. Use when: - User says "retro", "retrospective", "weekly review" - User asks "how was my week?", "engineering metrics", "velocity" - User wants to analyze commit patterns, work sessions, or code quality trends - User says "what did I ship?", "show me my stats"
darkroomengineering/cc-settings · ★ 29 · Code & Development · score 85
Install: claude install-skill darkroomengineering/cc-settings
# Engineering Retrospective Before starting work, create a marker: `mkdir -p ~/.claude/tmp && echo "retro" > ~/.claude/tmp/heavy-skill-active && date -u +"%Y-%m-%dT%H:%M:%SZ" >> ~/.claude/tmp/heavy-skill-active` Analyze commit history to produce velocity metrics, work patterns, and improvement suggestions with persistent history for trend tracking. **This skill is self-contained.** Do not read CLAUDE.md or agent definitions. ## Arguments - `/retro` — last 7 days (default) - `/retro 24h` or `/retro 14d` or `/retro 30d` — custom window - `/retro compare` — current 7d vs prior 7d - `/retro compare 14d` — current 14d vs prior 14d **Validation:** Only accept arguments matching `\d+[dhw]`, `compare`, or `compare \d+[dhw]`. Reject anything else with usage instructions. --- ## Step 1: Gather Raw Data Fetch latest from remote, then run 5 parallel git commands: ```bash # Fetch latest git fetch origin main 2>/dev/null # 1. Commits with timestamps, subject, hash, and stats git log origin/main --since="WINDOW_START" --format="%H|%aI|%s" --shortstat # 2. Per-commit numstat for test vs production LOC breakdown # Test files: paths matching test/|spec/|__tests__|*.test.|*.spec. git log origin/main --since="WINDOW_START" --format="%H" --numstat # 3. Sorted commit timestamps for session detection (local timezone) git log origin/main --since="WINDOW_START" --format="%aI" | sort # 4. Hotspot analysis (most frequently changed files) git log origin/main --since="WINDOW_START" --format