session-retro
Installation
SKILL.md
Session Retro
A retrospective on one coding-agent session, aimed at the agent's environment rather than at the people or the model. Every wasted call in a session has a cause outside the model that someone can edit: a file nobody pointed to, a test command written nowhere, a lint rule that does not exist, a safe command missing from the allowlist, a skill whose description never matched. This skill reads the transcript, counts where the session leaked time, and produces a short ranked list of changes, each naming the file to edit.
The output is not "the agent should be more careful". It is "add Tests: make test to
AGENTS.md" or "wire ruff check into the pre-commit hook", with the call numbers that
justify it.
When to Use
- After a session that went slow or wrong — many retries, a late-found bug, a wrong turn that cost twenty calls.
- After a session the user had to rescue — the user pasted information, overrode a decision, or approved the same command repeatedly.
- When tuning steering files —
CLAUDE.md,AGENTS.md,GEMINI.mdor Cursor rules have grown and nobody knows which lines still earn their place. - Before repeating a task type — the same kind of change is coming again and the last run was expensive.