Back to search
sprum
MarketplaceWorks with Claude CodeGitHub
Skills for Claude Code: /retro, a retrospective on the corrections in a session
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Checked today
Badge for your README
Markdown
[](/listings/sprum--claude-skills)HTML
<a href="/listings/sprum--claude-skills"><img src="/api/listings/sprum--claude-skills/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
/plugin marketplace add Sprum/claude-skills /plugin install retro@sprum
Then run `/retro` (or `/retro:retro`) after a session in which you had to correct Claude. Updates: `/plugin marketplace update sprum`.
For a whole team, add this to the project's `.claude/settings.json`; Claude Code then offers the install to everyone who opens the project:
{
"extraKnownMarketplaces": {
"sprum": { "source": { "source": "github", "repo": "Sprum/claude-skills" } }
},
"enabledPlugins": { "retro@sprum": true }
}What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
.claude-plugin/marketplace.json · Manifest · 16 lines
- {
- "name": "sprum",
- "owner": {
- "name": "Leo M."
- },
- "metadata": {
- "description": "Skills for Claude Code."
- },
- "plugins": [
- {
- "name": "retro",
- "source": "./plugins/retro",
- "description": "A retrospective on the corrections in a session: why they happened, and whether the context should change at all — and if so, where."
- }
- ]
- }
README.md · README · 74 lines
- # claude-skills
- Skills for [Claude Code](https://claude.com/claude-code).
- ## retro
- You corrected Claude in a session — once or several times. `/retro` goes through those corrections
- and asks, for each one: **why did it happen, and does anything need to change so it doesn't happen
- again?**
- For every correction it looks up, instead of guessing, whether the information already existed —
- in `CLAUDE.md`, the memory, the project docs, the skills that ran, the hooks — and names the cause:
- | Cause | Telltale sign |
- |---|---|
- | Missing | The information is nowhere. |
- | Not found | It exists, but somewhere Claude had no reason to read. |
- | Buried | It was in context, but too long, too general or without a reason. |
- | Ambiguous / contradictory | The instruction allows the wrong reading, or two places disagree. |
- | Assumed instead of asked | The decision belonged to the user. |
- | Mechanically checkable | A lint rule, test or hook could have caught it. |
- | Model error | The rule was clear and right there — and was ignored anyway. |
- Then it proposes a change, or none, and writes nothing until you approve.
- ### Why
- Most mistakes in agentic work are context problems — but not all of them. And every new rule has a
- price: it lengthens what every session loads and dilutes the rules already there. A retro that turns
- every correction into a new rule produces exactly the mistakes it is meant to prevent.
- So `retro` prefers, in this order: enforcing something mechanically (a hook, a test, a lint rule),
- improving an instruction that already exists, and only then adding something new — in the narrowest
- place that fits. If there's already a rule from an earlier correction on the same topic, that rule
- didn't work, and another one next to it won't either.
- **"Change nothing" is a complete result.**
- ### Example
- ```
- ### Committed to the default branch
- **What happened:** Claude committed straight to main instead of creating a feature branch.
- **Cause:** Buried — the branch rule is the 14th bullet of a long CLAUDE.md section, without a reason.
- **Change?** Yes — it happened before (there is a memory about it), so the existing rule isn't working.
- **Where:** .claude/settings.json
- **Change:** a PreToolUse hook that blocks `git commit` on main; delete the memory, the hook replaces it.
- ```
- ### Install
- ```
- /plugin marketplace add Sprum/claude-skills
- /plugin install retro@sprum
- ```
- Then run `/retro` (or `/retro:retro`) after a session in which you had to correct Claude. Updates:
- `/plugin marketplace update sprum`.
- For a whole team, add this to the project's `.claude/settings.json`; Claude Code then offers the
- install to everyone who opens the project:
- ```json
- {
- "extraKnownMarketplaces": {
- "sprum": { "source": { "source": "github", "repo": "Sprum/claude-skills" } }
- },
- "enabledPlugins": { "retro@sprum": true }
- }
- ```
- ## License
- [MIT](LICENSE)
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.