Postmortem
- 1.4k installs
- 23.5k repo stars
- Updated July 17, 2026
- alirezarezvani/claude-skills
postmortem is an agent skill that /em -postmortem — Honest Analysis of What Went Wrong.
About
/em -postmortem - Honest Analysis of What Went Wrong --- name: "postmortem" description: "/em -postmortem - Honest Analysis of What Went Wrong" --- # /em:postmortem - Honest Analysis of What Went Wrong **Command:** `/em:postmortem <event>` Not blame. The failed deal, the missed quarter, the feature that flopped, the hire that didn't work out. What actually happened, why, and what changes as a result. --- ## Why Most Post-Mortems Fail They become one of two things: **The blame session** - someone gets scapegoated, defensive walls go up, actual causes don't get examined, and the same problem happens again in a different form. **The whitewash** - "We learned a lot, we're going to do better, here are 12 vague action items." Nothing changes. Same problem, different quarter. It's a rigorous investigation into a system failure. Not "whose fault was it" but "what conditions made this outcome predictable in hindsight?" **The purpose:** extract the maximum learning value from a failure so you can prevent recurrence and improve the system.
- /em:postmortem - Honest Analysis of What Went Wrong
- What was the expected outcome?
- What was the actual outcome?
- When was the gap first visible?
- What was the impact (financial, operational, reputational)?
Postmortem by the numbers
- 1,434 all-time installs (skills.sh)
- +2 installs in the week ending Jul 29, 2026 (Skillselion tracking)
- Ranked #478 of 2,159 Testing & QA skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 31, 2026 (Skillselion catalog sync)
postmortem capabilities & compatibility
- Capabilities
- /em:postmortem — honest analysis of what went wr · what was the expected outcome? · what was the actual outcome? · when was the gap first visible? · what was the impact (financial, operational, rep
- Use cases
- documentation
What postmortem says it does
--- name: "postmortem" description: "/em -postmortem — Honest Analysis of What Went Wrong" --- # /em:postmortem — Honest Analysis of What Went Wrong **Command:** `/em:postmortem <event>` Not blame.
The failed deal, the missed quarter, the feature that flopped, the hire that didn't work out.
What actually happened, why, and what changes as a result.
**The whitewash** — "We learned a lot, we're going to do better, here are 12 vague action items." Nothing changes.
npx skills add https://github.com/alirezarezvani/claude-skills --skill postmortemAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.4k |
|---|---|
| repo stars | ★ 23.5k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 17, 2026 |
| Repository | alirezarezvani/claude-skills ↗ |
What problem does postmortem solve for developers using this skill?
/em -postmortem - Honest Analysis of What Went Wrong
Who is it for?
Developers who need postmortem patterns described in the cached skill documentation.
Skip if: Skip when docs are empty or the task is outside the skill's documented scope.
When should I use this skill?
/em -postmortem — Honest Analysis of What Went Wrong
What you get
Actionable workflows and conventions from SKILL.md for postmortem.
- postmortem report
- actionable process changes
Files
../../../c-level-advisor/executive-mentor/skills/postmortem/SKILL.md
Related skills
TddFollow test-driven development with a strict red-green-refactor loop when creating reliable features or fixing bugs.510k185k
Test Driven DevelopmentEnforce writing failing tests before any production implementation code.176k260kQaRun conversational QA sessions that turn user-reported bugs into well-written, domain-aware GitHub issues without manual ticket writing.164k185kMigrate To ShoehornAutomatically update TypeScript test files that rely on unsafe `as` type assertions by replacing them with type-safe partial objects from @total-typescript/shoehorn.151k185k
Webapp TestingVerify frontend behavior, debug UI issues, capture screenshots, and inspect logs of a running local web application using Playwright.121k164k
Playwright CliRun browser automation, generate element snapshots, inspect DOM attributes, and execute Playwright tests from the terminal.96.3k12.2kFAQ
What does postmortem do?
/em -postmortem — Honest Analysis of What Went Wrong
When should I use postmortem?
/em -postmortem — Honest Analysis of What Went Wrong
Is postmortem safe to install?
Review the Security Audits panel on this page before installing in production.