Postmortem
Recall or record confirmed reusable failure lessons. Use after a verified recurrence, review escape, failed gate, or explicit user request.
Install
npx skills add Dimon94/skills --skill postmortemgit clone --depth 1 https://github.com/Dimon94/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/postmortem ~/.claude/skills/postmortemPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Postmortem `postmortem` owns reusable failure memory. It does not own workflow state, review findings, remote delivery, ordinary failure logs, or environment change proposals (those belong to `retro`). Use exactly one mode: - `recall`: a recurrence, failed verification, or review escape may match a prior lesson; - `interrogate`: evidence is too thin to classify the lesson; - `record`: a confirmed reusable lesson, review escape, or explicit user request needs durable memory. Use `scripts/postmortem-contract.js#decidePostmortem` before any filesystem write. Ordinary failures and unconfirmed lessons do not record. Recall does not make historical evidence current; revalidate it against the present repro and code. When recall is needed, search `docs/postmortems/` only if it exists. Search by module, exact error, violated contract, failure class, and stable recurrence signature. A recurring pattern applies broadly; a special case applies only when its narrow recall condition matches. Before recording, require the symptom, evidence, root-cause status, lesson type, recall condition, and stable recurrence key. A suspected or unknown cause must never be written as confirmed. Update an existing matching recurrence rather than create a competing lesson. Durable records live under: ```text docs/postmortems/<lowercase-kebab-slug>.md ``` Call `scripts/postmortem-contract.js#recordPostmortem` only after the decision
Details
- Skill name
postmortem- Repository
- Dimon94/skills
- Path
skills/postmortem/SKILL.md- Repo updated
- 18 November 2026
FAQ
What does the Postmortem skill do?
Recall or record confirmed reusable failure lessons. Use after a verified recurrence, review escape, failed gate, or explicit user request.
How do I install the Postmortem skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add Dimon94/skills --skill postmortem. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Postmortem popular?
It lives in Dimon94/skills, which has 107 GitHub stars and 21 forks.
Related skills
Maintain Verification Skill
107Dimon94/skills
Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or "audit the verify skill".
Create Verification Skill
107Dimon94/skills
Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, "make a control skill for this repo", or when a project has no scripted way to prove UI/CLI/service behavior.
How
107Dimon94/skills
Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.
Principle Never Block on the Human
107Dimon94/skills
Apply when tempted to ask 'should I do X?' on reversible work.
Pi Loop
107Dimon94/skills
在 pi 里按节奏重复跑同一条提示词或 skill(/loop)。用户要在 pi 中定时轮询、按间隔或 cron 重复任务、让 issue-sweep 这类 skill 自定节奏持续跑,或安装、排查、卸载 pi-loop 扩展时使用。
Principle Redesign From First Principles
107Dimon94/skills
Apply when integrating a new requirement into an existing design.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.