postmortem

Creates post-mortem documentation from git logs and generates issue tracking items.

6|3|Updated Apr 12, 2026

Search Tags:#post-mortem #reliability #backlog #root-cause-analysis #process-improvement #incident-response

Ready to run

npx skills add https://github.com/carson-sweet/sweetclaude --skill postmortem-carson-sweet

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, python3, and includes scripts (resource) components.

What problem does it solve?

This skill removes the friction and ambiguity from incident reporting by providing a structured, repeatable framework for conducting post-mortems that focus on systemic improvements rather than blame.

Core Features & Use Cases

Timeline Reconstruction: Automatically gathers git logs and decision-log entries to build a chronological record of an incident.
Root Cause Analysis: Guides users through the 5 Whys methodology to identify systemic failures.
Actionable Backlog: Automatically generates and tracks high-priority backlog items to prevent incident recurrence.
Use Case: After a production hotfix, use this skill to document the timeline, identify the root cause, and create Jira-style issues for the necessary long-term fixes.

Quick Start

Invoke the postmortem skill to begin a structured analysis of the most recent incident or hotfix in your project.

Frequently Asked Questions about postmortem

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

FAQPage Schema

How do I create a post-mortem document after a production incident?▼

To create a post-mortem document, this skill guides you through timeline reconstruction, root cause analysis using the 5 Whys methodology, and action item generation to produce structured markdown documentation.

How does root cause analysis work for incident response?▼

Root cause analysis works by guiding users through the 5 Whys methodology to identify systemic failures, shifting the incident response focus from assigning blame to implementing systemic process improvements.

Can I automatically generate backlog items from a root cause analysis?▼

Yes, you can automatically generate and track high-priority backlog items from the root cause analysis, converting incident data directly into Jira-style issues to prevent incident recurrence.

Do I need git history access to reconstruct an incident timeline?▼

Yes, you need git history access because timeline reconstruction automatically gathers git logs and decision-log entries to build a chronological record of the incident within your software development lifecycle.

What is the best way to convert incident data into process improvements?▼

The best way to convert incident data into process improvements is using a structured framework that analyzes project state files and git history to generate actionable backlog items for long-term fixes.