retro
Engineering retrospective analyzing git commit history for shipping metrics, work patterns, and trends. Persistent history with trend tracking. Use weekly to review shipping velocity, or after milestones. Invoke with /retro [7d|14d|30d|24h] or /retro compare to see trends.
npx skills add majiayu000/claude-skill-registry --skill retro-josephneumann-claude-corps --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# /retro — Engineering Retrospective Analyze git commit history to produce shipping metrics, work patterns, and trends. Outputs a narrative summary to the conversation and saves a JSON snapshot to `.context/retros/` for trend tracking. ## Arguments ``` /retro → Last 7 days (default) /retro 24h → Last 24 hours /retro 14d → Last 14 days /retro 30d → Last 30 days /retro compare → 7-day window vs. prior 7 days /retro compare 14d → 14-day window vs. prior 14 days ``` **Validation**: If the argument doesn't match `<N>d`, `<N>h`, `compare`, or `compare <N>d`, print usage and stop. Do not guess. ## Rules - **Self-contained**: Do not read CLAUDE.md, reference.md, or other project docs. Everything needed is in this file. - **Output discipline**: ALL narrative output goes to the conversation. The ONLY file written is the JSON snapshot to `.context/retros/`. - **Use `origin/main`** for all git queries. Run `git fetch origin` first. If your repo uses a different default branch (e.g., `master`), adjust the git commands accordingly. - **Zero commits**: If the window contains zero commits, say so clearly and suggest trying a different window. Stop the pipeline. - **Round LOC/hour** to the nearest
- Arguments
- Rules
- Pipeline (13 Steps)
- Step 1: Gather Raw Data
- Step 2: Compute Core Metrics
- Step 3: Commit Time Distribution
- Step 4: Work Session Detection
- Step 5: Commit Type Breakdown
- Step 6: Hotspot Analysis
- Step 7: PR Size Distribution
- Step 8: Focus Score + Ship of the Week
- Step 9: Week-over-Week Trends
- Step 10: Streak Tracking
- Step 11: Load Prior Retro
git fetch origin Set window boundaries All commits on origin/main in window git log origin/main --since="$SINCE" --until="$UNTIL" --format="%H|%ai|%s" --no-merges Merge commits (PR boundaries) git log origin/main --since="$SINCE" --until="$UNTIL" --merges --format="%H|%ai|%s" Diff stats git log origin/main --since="$SINCE" --until="$UNTIL" --no-merges --numstat --format="%H" File change counts git log origin/main --since="$SINCE" --until="$UNTIL" --no-merges --name-only --format=""
What does the retro skill do?
Engineering retrospective analyzing git commit history for shipping metrics, work patterns, and trends. Persistent history with trend tracking. Use weekly to review shipping velocity, or after milestones. Invoke with /retro [7d|14d|30d|24h] or /retro compare to see trends.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill retro-josephneumann-claude-corps --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
