What is the primary goal of the Blameless Post-Mortem skill?

The goal is learning and prevention. It helps teams understand the systemic reasons why an incident occurred and creates a roadmap of action items to ensure it doesn't happen again, without pointing fingers at individuals.

Does it provide a structured report format?

Yes, it generates a complete report including an Executive Summary, Timeline, Impact assessment, Root Cause Analysis, and a prioritized list of Action Items.

What types of incidents should I use this for?

This skill is ideal for service outages, security breaches, data loss events, significant bugs that reached production, or even project management failures that delayed a launch.

How does this skill support SRE (Site Reliability Engineering) practices?

It automates the documentation phase of the incident lifecycle, ensuring that MTTR (Mean Time to Recovery) and detection triggers are captured consistently across all team post-mortems.

Blameless Post-Mortem

Name: Blameless Post-Mortem
Author: neurofoo

byneurofoo

•

Analytics & Monitoring

Conducts thorough, blameless incident analyses to identify root causes and document actionable lessons from outages or failures.

About

The Blameless Post-Mortem skill provides a structured framework for analyzing technical incidents, outages, or project failures within Claude Code. It guides the user through a systematic process of documenting timelines, assessing customer and business impact, and performing deep-dive Root Cause Analysis (RCA). By emphasizing systems and processes over individual blame, it helps engineering teams foster a culture of transparency and continuous improvement while ensuring that every incident results in concrete, trackable action items.

Key Features

Chronological timeline tracking for triggers, detection, and resolution
Action item generation with designated owners and deadlines
Blameless Root Cause Analysis (RCA) focusing on systemic factors
35 GitHub stars
Standardized incident reporting template with executive summaries
Multidimensional impact assessment for users and business metrics

Use Cases

Reviewing a failed software release to improve CI/CD pipelines and testing procedures.
Analyzing a production outage to identify why monitoring failed to alert the team.
Debriefing after a security incident to strengthen infrastructure and access controls.

About

Key Features

Chronological timeline tracking for triggers, detection, and resolution
Action item generation with designated owners and deadlines
Blameless Root Cause Analysis (RCA) focusing on systemic factors
35 GitHub stars
Standardized incident reporting template with executive summaries
Multidimensional impact assessment for users and business metrics

Use Cases

Reviewing a failed software release to improve CI/CD pipelines and testing procedures.
Analyzing a production outage to identify why monitoring failed to alert the team.
Debriefing after a security incident to strengthen infrastructure and access controls.