Menu
Post-invocation retrospective. Tracks skill issues and applies fixes automatically.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/edfenton/claude-skills --skill retro-createThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
Scaffold a pnpm + Turborepo MERN monorepo with Next.js, tooling, tests, CI, and optional GitHub repo creation.
Configure GitHub repository security with branch protection, Dependabot, security scanning, and CI workflows. Integrates with mern-scaffold, nean-scaffold, and iOS projects.
Harden a Vercel deployment with security headers, CSP, bot protection, and deployment configuration
Based on SOC occupation classification
| name | retro-create |
| description | Post-invocation retrospective. Tracks skill issues and applies fixes automatically. |
After any skill completes, review the session for issues and improve the skill to prevent recurrence.
Run automatically after every skill invocation completes (success or failure).
For each issue found:
<skill-dir>/retro.md (create the file if it does not exist)status: open only when the fix would change skill behavior in ways that cannot be verified in the current session. Require a resolution-hint on every open entry.After logging any status: open entry, append:
Open issues remain. Run /retro-resolve to process them.
## YYYY-MM-DD — <brief title>
- **type**: failed-command | user-correction | wrong-assumption | missing-step | outdated-instruction
- **skill**: <skill-name>
- **context**: <what happened>
- **root-cause**: <why it happened>
- **fix**: <what was changed> | `status: open` if not yet fixed
- **resolution-hint**: <what the fix should look like> (required for open entries)
- **files-changed**: <list of files edited, or "none">
status: open and note the concernresolution-hint, you can probably just apply it.status: open simply because the session is long or context is low.