retro
 · a weekly retro for your coding agent
★ github 
never type the same correction twice.
your coding agent keeps making the same mistakes.
you keep typing the same corrections.
every one of them is already written down,
in transcripts nobody reads.
── the evidence ────────────────────────────────
~/.claude/projects on one laptop: 1.3 GB.
last 45 days, one user:

  652  failed tool calls
  221  corrections typed by hand
  69  times the agent replied "you're right"
  40  Esc pressed mid-action
  8  sessions abandoned after a failure

none of it was ever read. until now.
── what retro does ─────────────────────────────
/retro reads your local Claude Code transcripts,
finds the friction that repeats, and turns it into
CLAUDE.md rules, with verbatim quotes as evidence.
you approve the diff. it applies.
it detects:

  corrections    "no, not like that", bug reports, redos
  admissions     the agent saying "you're right"
  repeated asks  same instruction across sessions
  rule requests  "remember, from now on always…"
  interrupts     Esc, plus what you said right after
  nudges         bare "continue" when it stalls
  retry loops    same call failing 3+ times
  abandoned      sessions that end on a failure
── install ─────────────────────────────────────
$ git clone https://github.com/craftwork-design/retro
$ cd retro && ./install.sh

then, inside Claude Code, in any project:

$ /retro          # last 30 days
$ /retro 90d      # custom window
$ /retro all      # every project on the machine

python 3.8+, stdlib only. nothing to pip install.
click the clone command to copy it.
── example output ──────────────────────────────
  pattern 1: wrong test command (9 failures, 6 sessions)
  evidence: `npm test` failed on jun 12, 14, 19…
  root cause: repo uses pnpm; CLAUDE.md never says so
  fix:
  + Run tests with `pnpm vitest run`, never `npm test`

  apply? (y/n)
── privacy ─────────────────────────────────────
one stdlib python file. zero network calls.
zero telemetry. your transcripts never leave
your laptop. read the entire source in ten minutes.
── vs /insights ────────────────────────────────
/insights gives you the big picture, monthly.
/retro turns specific failures into applied rules,
with quotes and dates attached. use both.