postmortem

Generate Amazon COE-style 5-whys postmortem reports from incident conversations and logs.

Updated Feb 22, 2026

Search Tags:#devops #troubleshooting #root cause analysis #postmortem #5 whys #incident report

Ready to run

npx skills add https://github.com/rahulrajaram/rahulskills --skill postmortem-rahulrajaram

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: postmortem
Source: https://github.com/rahulrajaram/rahulskills/tree/main/skills/postmortem
Command: npx skills add https://github.com/rahulrajaram/rahulskills --skill postmortem-rahulrajaram

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the generation of comprehensive Correction of Error (COE) postmortem reports, streamlining the process of analyzing incidents and identifying root causes.

Core Features & Use Cases

5-Whys Analysis: Systematically drills down to root causes using the 5-whys methodology.
Structured Reporting: Generates reports with clear sections for timeline, impact, action items, and lessons learned.
Use Case: After a critical service outage, use this Skill to quickly generate a formal postmortem report by providing the incident description, which the AI will then populate with details gathered from logs and system information.

Quick Start

Generate a postmortem report for the recent database connection failure.

Frequently Asked Questions about postmortem

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

FAQPage Schema

How do I generate a blameless postmortem report after an incident?▼

To generate a blameless postmortem report, provide the incident description and conversation logs. The tool analyzes the data and outputs a structured Correction of Error report using the 5-whys methodology to identify root causes without assigning blame.

What is a 5-whys root cause analysis and when do I need it for troubleshooting?▼

A 5-whys root cause analysis is a systematic troubleshooting method that drills down into an incident by asking why repeatedly. You need it after a critical service outage or failure to identify the underlying root cause rather than just treating symptoms.

How do I write an Amazon COE incident report from system logs and metrics?▼

To write an Amazon COE incident report, input your system logs and metrics. The tool gathers evidence from these sources and populates a formal report containing headers, executive summaries, timelines, impact assessments, and action items.

Can I automate incident report generation for DevOps workflows without external dependencies?▼

Yes, you can automate incident report generation for DevOps workflows without external dependencies. The tool operates standalone to analyze conversations, identify anti-patterns, and output structured postmortem reports directly or to a file.

What's the best way to structure a postmortem report for a critical service outage?▼

The best way to structure a postmortem report is to include clear sections for the timeline, impact assessment, 5-whys analysis, root causes, action items, and lessons learned. This ensures comprehensive documentation of the incident and its resolution.

What should I do if my 5-whys analysis is not finding the actual root cause?▼

If your 5-whys analysis is not finding the actual root cause, ensure you are providing comprehensive conversation logs and system metrics. The tool relies on gathering evidence from these inputs to systematically drill down and identify anti-patterns accurately.