incident-review

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

1|Updated Jun 28, 2026
One-click install
npx skills add https://github.com/whmathews15/DEX-Personal-Operating-System --skill incident-review-whmathews15
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident-review
Source: https://github.com/whmathews15/DEX-Personal-Operating-System/tree/main/.claude/skills/_available/engineering/incident-review
Command: npx skills add https://github.com/whmathews15/DEX-Personal-Operating-System --skill incident-review-whmathews15

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a messy incident into a clear post-mortem so teams can understand what happened, why it happened, and what to do differently next time.

Core Features & Use Cases

  • Timeline reconstruction: Capture the sequence of events, impact, and duration for a complete incident narrative.
  • Root cause analysis: Prompt for deeper investigation into causes, missed signals, and contributing factors.
  • Action item tracking: Document immediate fixes, prevention measures, and monitoring improvements in a structured format.
  • Use case: After a production outage or customer-impacting bug, use this Skill to create a shared incident review that preserves lessons learned and assigns follow-up work.

Quick Start

Use the incident-review skill to document the post-mortem for the recent service outage and save the completed review in the learnings folder.

Frequently Asked Questions about incident-review

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

FAQPage Schema
How do I document an incident post-mortem after a production outage?

An incident post-mortem documents the timeline, impact, root cause, and action items of a production outage. This Skill structures that capture process to preserve lessons learned and assign follow-up work for recurrence prevention.

What is root cause analysis and how does it work for service failures?

Root cause analysis for service failures investigates underlying causes, missed signals, and contributing factors behind an incident. This Skill prompts deeper investigation during the post-mortem to move beyond symptoms and identify what truly went wrong.

Can I use this for tracking action items and prevention measures after an outage?

Yes, tracking action items after an outage is a core feature. It documents immediate fixes, prevention measures, and monitoring improvements in a structured format so engineering teams can assign and monitor follow-up work.

Does this work for recurring process breakdowns or only major service outages?

This works for both major service outages and recurring process breakdowns. It applies to any engineering or operations team reviewing service failures, capturing structured incident details regardless of the outage severity.

What's the best way to reconstruct an incident timeline for a post-mortem?

The best way to reconstruct an incident timeline is capturing the sequence of events, impact, and duration. This Skill structures that timeline reconstruction to create a complete incident narrative for your shared review.