retrolisted
Install: claude install-skill ehnruiz/claude-skills
# Retro
A retro improves the agent's **environment**: the checks, docs and pointers that the next session in this project will run into. It ends with one change made in the project, which the user reviews and commits. Credit and license: `LICENSE.md` in this folder.
## Steps
1. **Load the style guide.** Call the Skill tool with `writing-for-agents`. Every doc or rule this retro writes is read by an agent, and that skill says how to write one so it is followed the same way every run.
2. **Read the session.** Use the session the user names; with none named, use the current one. For an earlier session, read its transcript rather than working from memory: Claude Code keeps them as `.jsonl` files under `~/.claude/projects/<project slug>/`. Note each place the agent searched for a long time, made a mistake, retried, or lacked a fact it needed.
3. **Find candidates** in the categories below. Each candidate names the moment in the session (the tool call, the error, the retry) and the change that would have prevented it.
4. **Present them to the user, most severe first.** Severity is what the problem cost or would cost again: a mistake that shipped outranks a slow search, a slow search outranks a wasted tool call.
5. **Build the one the user picks.** Make the change in the project: the test, the lint rule, the CI step, the doc or the pointer. Run it and report its exit code. A new check must fail on the mistake it is meant to catch before it counts, so show it red on that mistake,