postmortem

Generate structured Postmortem Records from git history and incident data.

Updated Feb 23, 2026

Search Tags:#timeline #postmortem #root-cause #hardening #blast-radius #incident-management #pmr

Ready to run

npx skills add https://github.com/0xHoneyJar/construct-hardening --skill postmortem-0xhoneyjar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: postmortem
Source: https://github.com/0xHoneyJar/construct-hardening/tree/main/skills/postmortem
Command: npx skills add https://github.com/0xHoneyJar/construct-hardening --skill postmortem-0xhoneyjar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and maintain structured Postmortem Records (PMRs) from incidents by reconstructing timelines from git history, aggregating root-cause classification, mapping blast radius to data consumers, and surfacing signal gaps that enable defense hardening.

Core Features & Use Cases

Generate a complete PMR from incident data, including timeline, root cause, blast radius, and hardening actions.
Trace provenance from commits, issues, and PRs to ensure auditability and continuous learning.
Apply the PMR to sprint planning and long-term hardening workflows by feeding into downstream tools like hardened action specs.

Quick Start

Provide an incident reference or description and the skill will generate a complete PMR from available git history and issues.

Frequently Asked Questions about postmortem

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

FAQPage Schema

How do I generate a structured postmortem from git history and issue reports?▼

Generate a structured postmortem by providing an incident reference to reconstruct timelines from git history, aggregate root-cause classification, map blast radius, and surface signal gaps for defense hardening.

What is blast-radius mapping in incident management?▼

Blast-radius mapping in incident management identifies data consumers affected by a software incident by tracing provenance from commits and issues, ensuring auditability and continuous learning.

Can I trace provenance from commits and PRs when creating a postmortem record?▼

Yes, you can trace provenance from commits, issues, and PRs to ensure auditability and continuous learning when generating a reproducible postmortem record from multi-source incident histories.

What is the best way to classify root causes for a software incident?▼

The best way to classify root causes for a software incident is using a documented workflow with root-cause taxonomy that reconstructs timelines and applies signal-gap analysis for hardening action generation.

How do I surface signal gaps to generate hardening actions after an incident?▼

Surface signal gaps by applying signal-gap analysis during postmortem generation, which identifies missing detection signals and produces hardening actions for long-term defense workflows.

Do I need any dependencies to automate postmortem generation from incident data?▼

No dependencies are required to automate postmortem generation from incident data; the skill independently reconstructs timelines and maps blast radius using a documented workflow with provenance tracking.