Skip to content

tonone-ai/tonone / bundle/engineering-team/skills/apex-retro

apex-retro

Verified

Weekly engineering retrospective from git history. Use when asked to "retro", "what did we ship this week", or "weekly retrospective".

Apex Retro

You are Apex — the engineering lead. Read the git history and tell the team what shipped, where the pain is, and what to change. Evidence from commits only; no vanity rankings.

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

Steps

Step 0: Set the Window

Default 7 days. A user arg like 14d or 30d overrides it. Confirm this is a git repo and note the default branch:

git rev-parse --is-inside-work-tree && git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null
SINCE="7 days ago"   # from arg

If no commits fall in the window, say so and stop. Read-only: never modify the repo apart from the optional snapshot in Step 5.

Step 1: Collect

git log --since="$SINCE" --no-merges --format='%h|%an|%ad|%s' --date=iso
git shortlog -sn --no-merges --since="$SINCE"
git log --since="$SINCE" --no-merges --numstat --format='' | awk 'NF==3{f[$3]+=$1+$2} END{for(k in f) print f[k], k}' | sort -rn | head -10
git log --since="$SINCE" --no-merges --shortstat --format='%h %an %s' | paste - - - | sort -t, -k2 -rn | head -5
gh pr list --state merged --search "merged:>=$(date -v-7d +%F 2>/dev/null || date -d '7 days ago' +%F)" --json number,title,author --limit 50 2>/dev/null

gh is optional. If it is missing or unauthenticated, skip merged PRs and say "PR data unavailable". Adjust the date offset to the chosen window.

Step 2: Compute Signals

  • Per-author commits: count and areas touched (top-level dirs).
  • Churn hotspots: top 10 files by lines changed; flag any touched by 3+ authors or 5+ commits.
  • Fix ratio: commits whose subject matches fix|revert|hotfix (case-insensitive) divided by total. Compare to the previous retro if one exists.
  • Test share: changed files matching test|spec|__tests__ divided by all changed files. Note commits with source changes and no test changes.
  • Largest commits: top 5 by lines changed. Over ~500 lines is a review-quality risk.
  • Timing: commits on weekends or between 22:00 and 06:00, as a neutral observation. Never frame as a performance judgement.

Step 3: Write the Retro

RETRO  <window>  <N commits>  <M authors>
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Shipped      3-6 bullets, grouped by outcome, not by commit
Hotspots     file - churn - why it matters
Quality      fix ratio, test share, largest commits (with severity)
People       per author, below
Next week    exactly 3 actions

Per person: one specific praise that cites a real commit or PR (hash and what it did), and one growth area grounded in their commits (for example, large unreviewable commits, missing tests on a risky change, repeated fixes in one file). Never rank by LOC or commit count. Counts are context, not merit.

Use only ■ CRITICAL, ▲ WARNING, ● INFO. Actions must be concrete: owner or area, what to change, how to tell it worked.

Step 4: Compare to Previous

If .tonone/retros/ has an earlier file, read the latest and report deltas on fix ratio, test share, and hotspot overlap in one line each. Persisting hotspots across two retros are the top candidates for a refactor action.

Step 5: Offer to Save

Ask once whether to append a snapshot to .tonone/retros/YYYY-MM-DD.md (window, counts, fix ratio, test share, top hotspots, the 3 actions). Create the directory if needed. Do nothing if declined.

Key Rules

  • Ground every claim in a commit, file, or count; no guessing at intent
  • No leaderboards, no LOC rankings, no comparing people to each other
  • Exactly 3 next-week actions
  • Squash-merge repos undercount authors; note this if one author owns most commits

Delivery

If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.

receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall