skills.rest
louderthanthunderx1
louderthanthunderx1COMMUNITY
Explore all skills by this author →
GitHub

post-mortem

Create canonical engineering post-mortems documenting root cause, mechanism, fix, and validation.

Updated May 21, 2026
Search Tags:#post-mortem#root-cause#bug-fix#incident-review#engineering-record#blameless-analysis
One-click install
npx skills add https://github.com/louderthanthunderx1/loki-skills --skill post-mortem-louderthanthunderx1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: post-mortem
Source: https://github.com/louderthanthunderx1/loki-skills/tree/main/skills/engineering/post-mortem
Command: npx skills add https://github.com/louderthanthunderx1/loki-skills --skill post-mortem-louderthanthunderx1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-mortems provide a structured, blameless record of a bug fix that helps engineers understand what happened, why it happened, and how to prevent recurrence.

Core Features & Use Cases

  • Canonical record of root cause, mechanism, fix, and validation to speed future debugging.
  • Blameless analysis that focuses on process gaps and system behavior rather than individuals.
  • Shareable learnings to inform stakeholders, improve reviews, and guide process improvements.

Quick Start

Draft the post-mortem immediately after a fix is validated, using the four mandatory sections and links to the corresponding PR.

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 fixing a bug?▼

A blameless post-mortem focuses on process gaps and system behavior rather than individuals, providing a structured record of the root cause, mechanism, fix, and validation to prevent recurrence.

What do I need to create an engineering incident review?▼

Creating an engineering incident review requires four inputs: a reliable reproduction, a known root cause, an identified fix, and a validated fix applied to the bug.

When should I document a root-cause analysis for a bug fix?▼

Document a root-cause analysis immediately after the fix is validated, using mandatory sections and links to the corresponding PR to speed future debugging and guide process improvements.

Can I use incident reviews to document Jira tickets or PR-linked bug fixes?▼

Yes, incident reviews are useful for documenting fixes in Jira or PR-linked tickets, creating shareable learnings to inform stakeholders and improve reviews across engineering teams.

What is the best way to record engineering post-mortems for future debugging?▼

The best way to record engineering post-mortems is by capturing the canonical story of the bug immediately after validation, ensuring the root cause and fix mechanism are preserved to speed up future debugging.

Related Skills

Explore More Software Engineering Skills→
thananonthananon
3.1k

post-mortem

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

Community
Advanced
vertivolatamvertivolatam
1

Post-Mortem Process

Guide blameless post-mortems with timeline reconstruction and 5 Whys analysis.

Official
Advanced
tinner-deinnotinner-deinno

post-mortem

Generate a canonical engineering post-mortem record for a fixed bug.

Community
Intermediate
whmathews15whmathews15
1

incident-review

Document incident post-mortems with timeline, impact, root cause, and action items.

Community
Intermediate