skills.rest
thananon
thananonCOMMUNITY
Explore all skills by this author →
GitHub

post-mortem

Draft a canonical post-mortem documenting root cause, fix, validation, and learnings.

3.1k|415|Updated May 20, 2026
Search Tags:#debugging#post-mortem#root-cause#bug-fix#incident#blameless#engineering-record
One-click install
npx skills add https://github.com/thananon/9arm-skills --skill post-mortem-thananon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: post-mortem
Source: https://github.com/thananon/9arm-skills/tree/main/skills/engineering/post-mortem
Command: npx skills add https://github.com/thananon/9arm-skills --skill post-mortem-thananon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write the canonical engineering record after a bug fix, detailing root cause, mechanism, fix, validation, and learnings to prevent recurrence.

Core Features & Use Cases

  • Structured template: enforces mandatory sections (Summary, Root cause, Fix, Validation, Learnings).
  • Blameless, actionable: focuses on processes and improvements rather than people.
  • Invocation cues: suggests trigger phrases like /post-mortem or "document this fix" to generate the artifact.

Quick Start

Provide a draft post-mortem that includes Summary, Root cause, Fix, and Validation based on a debug session's notes.

Frequently Asked Questions about post-mortem

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

FAQPage Schema
How do I write a blameless post-mortem after an incident?▼

Draft a post-mortem by providing notes from a debug session that include a reliable repro, known root cause, defined fix, and validated outcome to generate a structured engineering record.

What do I need to generate an engineering post-mortem?▼

An engineering post-mortem contains mandatory sections for Summary, Root cause, Fix, Validation, and Learnings, preserving code identifiers and presenting findings in a traceable format for engineering audiences.

When do I need to document a root-cause analysis for a bug fix?▼

You need a root-cause analysis after a confirmed bug fix to document the mechanism and validation, ensuring the engineering record is blameless, actionable, and traceable for future reference.

Does the post-mortem format work for incidents without a clear root cause?▼

No, the post-mortem format requires a known root cause, reliable repro, defined fix, and validated outcome before generation to accurately document the incident mechanism and prevent recurrence.

Related Skills

Explore More Software Engineering Skills→
s6804062612242-afks6804062612242-afk

post-mortem

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

Community
Advanced
davekilleendavekilleen
461

incident-review

Generate structured incident post-mortems with root cause analysis and action items.

Community
Intermediate
TestAny-ioTestAny-io
79

debug

Diagnose Testany test failures by analyzing execution logs and identifying root causes.

Official
Intermediate
NotysotyNotysoty
9

Incident Postmortem Writer

Generate structured blameless incident postmortems from timelines or Slack threads.

Community
Advanced