Does this skill help with prevention?

Yes, a core component of the skill is identifying what testing, monitoring, or design changes would have caught the issue before it reached production.

How does this skill help with Root Cause Analysis (RCA)?

The skill guides you through formal frameworks like the '5 Whys' or Fishbone diagrams to dig past surface-level errors (like typos) to find the underlying systemic issues.

What is a blameless postmortem?

A blameless postmortem is a practice where the focus is placed on systemic failures and process improvements rather than blaming individuals, encouraging honest reporting and better learning.

What data should I provide for an effective postmortem?

For the best results, provide logs, timestamps of events, team recollections, system load data, and details of any recent changes or deployments.

Postmortem Analysis

Name: Postmortem Analysis
Author: sethdford

bysethdford

•

分析と監視

Conducts blameless incident reviews and root cause analysis to document system failures and prevent future recurrence.

This skill empowers Claude to guide engineering teams through a structured postmortem process following system failures or production incidents. Grounded in Site Reliability Engineering (SRE) principles, it facilitates the creation of a factual, 5-minute interval timeline, identifies systemic root causes using the 5 Whys method, and helps define actionable, measurable improvements. By focusing on process and architectural gaps rather than individual blame, it ensures that every incident becomes a learning opportunity that strengthens system resilience and prevents the repetition of previous errors.

主な機能

019 GitHub stars

02Identification of specific prevention strategies and testing gaps

03Blameless root cause analysis (RCA) focusing on systems and processes

04Precise event timeline construction with 5-minute interval labeling

05Structured 5 Whys and Fishbone diagram methodologies

06Generation of assignable, measurable, and actionable improvement items

ユースケース

01Analyzing a production outage to identify architectural vulnerabilities

02Reviewing high-severity bugs that bypassed existing CI/CD gates

03Documenting 'near-miss' incidents to improve observability and monitoring

主な機能

019 GitHub stars

02Identification of specific prevention strategies and testing gaps

03Blameless root cause analysis (RCA) focusing on systems and processes

04Precise event timeline construction with 5-minute interval labeling

05Structured 5 Whys and Fishbone diagram methodologies

06Generation of assignable, measurable, and actionable improvement items

ユースケース

01Analyzing a production outage to identify architectural vulnerabilities

02Reviewing high-severity bugs that bypassed existing CI/CD gates

03Documenting 'near-miss' incidents to improve observability and monitoring