- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add codeaholicguy/ai-devkit --skill dev-retro -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add codeaholicguy/ai-devkit --skill dev-retro -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add codeaholicguy/ai-devkit --skill dev-retro -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add codeaholicguy/ai-devkit --skill dev-retro -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/codeaholicguy/ai-devkit/tree/HEAD/skills/dev-retroFrom the publisher
Turn what went wrong into fixes that stop it recurring. Not a status summary: use session-compact for handoff state.
Pick the highest rung that works:
AGENTS.md / CLAUDE.md, docs.memory entry, only for knowledge that cannot be enforced. Search first; update instead of duplicating.git log and diff for the range, failed or retried commands, hook/CI failures, task evidence, user corrections. Use the session transcript when available (agent sessions, session-compact); do not require it.verify (a new check must fail on the old state when practical), and commit per the user's workflow.Pause when evidence is missing, a fix needs a team or ownership decision, or the root cause is unclear; hand unclear failures to dev-debug.
AI DevKit · Run an evidence-based retrospective on finished work (feature, session, incident) and turn friction into durable fixes, automation first. Use when users ask for a retro, lessons learned, p
---name: dev-retrodescription: AI DevKit · Run an evidence-based retrospective on finished work (feature, session, incident) and turn…---# skills/dev-retro/SKILL.mdOverview
AI DevKit · Run an evidence-based retrospective on finished work (feature, session, incident) and turn friction into durable fixes, automation first. Use when users ask for a retro, lessons learned, post-mortem, or "what went wrong", or when another skill offers one after a feature or fix.
FAQ
Download skills/dev-retro/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/codeaholicguy/ai-devkit.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.