Skip to content
Skill

Incident postmortem

Use when an outage, production incident, or significant service degradation has occurred and the team needs a blameless post-mortem / RCA do

Install
Scripts
None
Platforms
Claude Code, Codex, Cursor
GitHub stars
41.3K
Last commit
1 day ago
License
MIT
Listing updated
today

When your agent uses it

Use when an outage, production incident, or significant service degradation has occurred and the team needs a blameless post-mortem / RCA document in the Google SRE format. Triggers on phrases like "write a post-mortem", "incident review", "what went wrong", "outage report", "root cause analysis", "RCA", or "fishbone". Collects incident inputs from the user, uses a fishbone (Ishikawa) diagram to surface candidate causes, drills the strongest branches with 5 Whys, and produces typed action items. Outputs Markdown by default, with HTML, DOCX, or PDF on request.

From the skill's SKILL.md. Your agent reads this description to decide when to load the skill.

What it can access

From a static check of its 3 files (17 KB) on GitHub on 17 November 2026. Nothing was run. Read the files before you install a skill: it can tell your agent to run anything its tools allow.

Install

Copy the skill folder to ~/.claude/skills/incident-postmortem to use it in all your projects:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/incident-postmortem &&
cp -R "$tmp/skills/incident-postmortem" ~/.claude/skills/incident-postmortem &&
rm -rf "$tmp"

For one project only, put the folder in .claude/skills/incident-postmortem inside it instead.

Claude Code docs on skills

Copy the skill folder to ~/.agents/skills/incident-postmortem to use it in every repository:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/incident-postmortem &&
cp -R "$tmp/skills/incident-postmortem" ~/.agents/skills/incident-postmortem &&
rm -rf "$tmp"

For one repository only, put the folder in .agents/skills/incident-postmortem inside it instead.

Codex docs on skills

Copy the skill folder to ~/.cursor/skills/incident-postmortem to use it in every project:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/incident-postmortem &&
cp -R "$tmp/skills/incident-postmortem" ~/.cursor/skills/incident-postmortem &&
rm -rf "$tmp"

For one project only, put the folder in .cursor/skills/incident-postmortem inside it instead.

Cursor docs on skills

Run in a terminal (add --scope workspace to install it for the current workspace only):

gemini skills install https://github.com/github/awesome-copilot.git --path skills/incident-postmortem

Or copy the folder to ~/.gemini/skills/incident-postmortem yourself.

Gemini CLI docs on skills

For GitHub Copilot in VS Code, copy the skill folder to ~/.copilot/skills/incident-postmortem:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/incident-postmortem &&
cp -R "$tmp/skills/incident-postmortem" ~/.copilot/skills/incident-postmortem &&
rm -rf "$tmp"

For one project only, put the folder in .github/skills/incident-postmortem inside it instead.

VS Code docs on skills

Get the folder:

git clone --depth 1 https://github.com/github/awesome-copilot.git

Then copy awesome-copilot/skills/incident-postmortem into your agent's skills folder as incident-postmortem. Agents that support SKILL.md read one folder per skill.

The SKILL.md format

Incident postmortem FAQ

How do I install Incident postmortem in Claude Code?

Copy the skill folder from GitHub to ~/.claude/skills/incident-postmortem to use it in all your projects, or to .claude/skills/incident-postmortem in one project.

Does Incident postmortem run scripts?

No. It is instructions only, with no scripts. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.

Which AI agents can use Incident postmortem?

Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.

What are the best alternatives to Incident postmortem?

The closest alternatives to Incident postmortem are DOCX, XLSX, PDF, Convert word to md and Markdown to word mermaid.

More from github/awesome-copilot

  1. Design or review infrastructure, deployment, CI/CD, Docker, Kubernetes, health checks, rollback, feature flags, production readiness, and mo

    • Open source
    • 41.3K GitHub stars
    • Cloud and infrastructure
  2. Stop coding agents from shipping generic UI

    • Open source
    • 41.3K GitHub stars
  3. Cross-references C# Web API controllers/DTOs against their TypeScript/JavaScript consumers (React, Angular, Vue, Svelte, Node.js, or hand-wr

    • Open source
    • 41.3K GitHub stars
  4. Serves as a reviewer of the codebase with instructions on looking for Apple App Store optimizations or rejection reasons.

    • Open source
    • 41.3K GitHub stars
  5. Triage and resolve Arch Linux issues with pacman, systemd, and rolling-release best practices.

    • Open source
    • 41.3K GitHub stars

Alternatives to Incident postmortem

  1. DOCX

    Skill

    Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files)

    • 196K GitHub stars
    • Files and documents
  2. XLSX

    Skill

    Use this skill any time a spreadsheet file is the primary input or output

    • 196K GitHub stars
    • Files and documents
  3. PDF

    Skill

    Use this skill whenever the user wants to do anything with PDF files

    • 196K GitHub stars
    • Files and documents
  4. Converts Word (.docx) documents into Markdown so their contents can be accurately analyzed, summarized, searched, or extracted from

    • Open source
    • 41.3K GitHub stars
    • Files and documents
  5. Export Markdown containing Mermaid code fences to Word (.docx) with embedded SVG diagrams and PNG fallbacks

    • Open source
    • 41.3K GitHub stars
    • Files and documents
  6. Update a markdown file section with an index/table of files from a specified folder.

    • Open source
    • 41.3K GitHub stars
    • Files and documents