incident-postmortem
Use when an outage, production incident, or significant service degradation has occurred and the team needs to write a structured blameless post-mortem. Triggers on phrases like "write a post-mortem", "incident review", "what went wrong", "outage report", "root cause analysis", or "RCA". Covers timeline reconstruction, contributing factor analysis, impact quantification, and action item generation with owners.
Profile →npx skills add github/awesome-copilot --skill incident-postmortem --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Incident Post-Mortem Guide a team through writing a structured, blameless post-mortem after a production incident. The output is a document that builds shared understanding, identifies root causes without blame, and produces concrete action items to prevent recurrence. ## Blameless Principle Systems fail, not people. The goal is to understand HOW the incident happened — not WHO caused it. Avoid language like "X forgot to", "Y should have known". Use "the system did not", "the process lacked", "the alert did not fire". ## When to Use - Production outage or service degradation has been resolved - A significant near-miss occurred (would have been an incident if caught later) - User-facing errors, data loss, or SLA breach happened - Team wants to capture learnings before context fades **Not for:** Minor bugs caught in staging, planned maintenance windows, or incidents with no learning value. ## Input Requirements Gather these details before writing the post-mortem. Ask for anything missing: ### Incident Metadata - Incident title (short, descriptive) - Date and time of detection (with timezone) - Date and time of resolution - Severity / impact level (P1–P4 or equivalent) - Incident co
- Blameless Principle
- When to Use
- Input Requirements
- Incident Metadata
- Impact
- Timeline Events
- Contributing Factors
- Process
- Step 1 — Gather Metadata
- Step 2 — Reconstruct Timeline
- Step 3 — Root Cause Analysis
- Step 4 — Impact Quantification
- Step 5 — Action Items
- Step 6 — Write the Document
What does the incident-postmortem skill do?
Use when an outage, production incident, or significant service degradation has occurred and the team needs to write a structured blameless post-mortem. Triggers on phrases like "write a post-mortem", "incident review", "what went wrong", "outage report", "root cause analysis", or "RCA". Covers timeline reconstruction, contributing factor analysis, impact quantification, and action item generation with owners.
How do I install it?
Run `npx skills add github/awesome-copilot --skill incident-postmortem --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.