Draft incident postmortems with timeline, root causes, and corrective actions.
npx skills add https://github.com/ChazzCoin/claude-kit --skill postmortem-chazzcoin
Please help me install this Agent Skill. Skill: postmortem Source: https://github.com/ChazzCoin/claude-kit/tree/main/kit/skills/postmortem Command: npx skills add https://github.com/ChazzCoin/claude-kit --skill postmortem-chazzcoin
Draft a postmortem for an incident — production outage, broken deploy, data loss, regression caught late. Captures timeline, root cause, contributing factors, what we changed (or will change) to prevent recurrence. Stored in docs/postmortems/YYYY-MM-DD-slug.md and logged in AUDIT.md. Triggered when something broke — e.g. "/postmortem", "write up what happened", "we need to capture this incident", "draft a postmortem for the deploy that broke".
Draft a postmortem file at docs/postmortems/YYYY-MM-DD-short-slug.md and append the corresponding AUDIT.md entry.
High-intent search queries and answers about installing and using this skill.
An incident postmortem captures the timeline, root causes, contributing factors, and action items following an outage or data loss. It follows a blameless, systems-focused process to drive lasting fixes and prevent recurrence.
A blameless postmortem is a systems-focused review that identifies root causes and contributing factors without targeting individuals. It drives lasting fixes by focusing on process and system improvements rather than personal blame.
You document an incident timeline by drafting a templated Markdown file stored under docs/postmortems/YYYY-MM-DD-slug.md. This file captures the timeline, root causes, and corrective actions, and links to an AUDIT.md entry for traceability.
Yes, you can use a structured postmortem template for data loss incidents. The template captures the incident timeline, root-cause chains, and contributing factors, ensuring publication-ready documentation for significant degradation or data loss events.
The best way to log incident reviews for traceability is to append an entry to AUDIT.md. This links directly to the postmortem Markdown file, ensuring every incident documentation effort is tracked and auditable.
emilneuraz-aiAutomate blameless postmortems with root cause analysis, timelines, and follow-ups.
timequityCreate blameless postmortems documenting root-cause analyses with structured markdown templates.
tianjianjiangGuide structured, blameless incident postmortems with root cause analysis and action-item tracking.
Prat011Extract key concepts and decisions from conversations into structured Notion pages.
