post-mortem

Generate engineering post-mortems documenting root cause, fix, validation, and lessons learned.

Updated May 25, 2026

Search Tags:#post-mortem #root-cause #bug-fix #blameless #incident-analysis #engineering-report

Ready to run

npx skills add https://github.com/s6804062612242-afk/my-distro-linux-base-kernel --skill post-mortem-s6804062612242-afk

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: post-mortem
Source: https://github.com/s6804062612242-afk/my-distro-linux-base-kernel/tree/main/skills/engineering/post-mortem
Command: npx skills add https://github.com/s6804062612242-afk/my-distro-linux-base-kernel --skill post-mortem-s6804062612242-afk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The canonical post-mortem template ensures engineers capture the complete narrative of a bug fix—root cause, mechanism, fix, validation, and lessons learned—in a reusable artifact that supports fast onboarding and audit trails.

Core Features & Use Cases

Provides mandatory sections: Summary, Root cause, Fix, Validation, and How it was found, with blameless framing.
Enforces a consistent, evidence-driven structure to help teams learn from incidents and improve processes.
Enables knowledge transfer by standardizing how post-mortems are written, stored, and referenced in future tickets.

Quick Start

Draft the post-mortem immediately after a fix is validated using this template.

Frequently Asked Questions about post-mortem

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is a blameless engineering post-mortem and when do I need one?▼

An engineering post-mortem requires a reliable reproduction, a known root cause, an identified fix, and validation to be present. You must draft the post-mortem immediately after the bug fix is validated to ensure accurate evidence capture.

How do I write a post-mortem report after a bug fix?▼

A blameless post-mortem focuses on systemic root cause analysis and mechanism documentation rather than individual fault. This framing enforces a consistent, evidence-driven structure to help teams learn from incidents and improve engineering processes.

Do I need a reliable reproduction before drafting an incident analysis?▼

Yes, an incident analysis post-mortem requires a reliable reproduction, a known root cause, an identified fix, and validation to be present. These prerequisites ensure the documented narrative and evidence trail are accurate and actionable.

What is the best way to structure an engineering report for incident analysis?▼

The best way to structure an incident analysis engineering report is using mandatory sections: Summary, Root cause, Fix, Validation, and How it was found. This consistent, evidence-driven structure standardizes knowledge transfer and supports audit trails.