Individual skill
postmortem
Explain why a change, incident or session went as it did, separating proven causes from coincidence. Use when: asked for a postmortem, retro or root-cause write-up.
skills/postmortem/SKILL.md
Source commit 7547dab37a18f36def54b25e0c81eb39ef9dffef
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Local scripts
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 452
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- claude-code Repository topic
- claude-code-plugins Repository topic
- claude-marketplace Repository topic
- devops Repository topic
- codex Repository topic
- codex-plugin Repository topic
- cursor Repository topic
- opencode-plugin Repository topic
- claude Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 7,884 bytesscripts/validate.shruns · 966 bytes
Read excerpt
# Postmortem
Answer an explicit retrospective causal question about a completed or stopped
goal, session, change or incident from its actual intent, outcome and judgment evidence.
Neighbours: how a plan not yet run could fail is [Premortem](../premortem/SKILL.md);
whether a finished change meets acceptance is [Validate](../validate/SKILL.md).
## First check: correlation or cause?
Treat every causal statement as a hypothesis, including the one the caller
arrives with. Promoting a claim from correlation to cause requires all three:
- a stated mechanism: the specific path by which the condition produced the
outcome, in terms a reader could check against the subject;