Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From debugging
Comprehensive postmortem with timeline, RCA, prevention, and action items.
npx claudepluginhub sethdford/claude-skills --plugin engineer-debuggingHow this command is triggered — by the user, by Claude, or both
Slash command
/debugging:write-postmortem incident-summary or timeline-notesThe summary Claude sees in its command listing — used to decide when to auto-load this command
Chain these steps: 1. Use the `postmortem-analysis` skill to structure the document 2. Use the `root-cause-analysis` skill to develop RCA section 3. Use the `log-analysis` skill for accurate timeline with evidence 4. Generate complete postmortem with action items and ownership After completion, suggest: "Review this with the team and assign owners to action items."
/postmortemGenerates a blameless postmortem document for incidents, experiments, or releases, using a structured template with timeline, root cause analysis (5 Whys), impact summary, and action items.
/write-postmortemConduct post-incident review and document findings, root causes, and preventive measures.
/postmortem-summaryGenerates a structured postmortem summary for a resolved Rootly incident, including timeline, root cause analysis, impact, detection, response, related incidents, action items, and metrics.
/postmortemGenerates a Google-SRE-style blameless postmortem from an incident tracker URL or ID. Gathers evidence, builds a timeline, confirms scope with the user, then writes and renders the document.
/incidentManages incident response: classifies SEV1-4 severity, builds timelines with evidence, performs 5 Whys root cause analysis, generates blameless post-mortems with action items and metrics. Outputs Markdown docs and git commits.
Share bugs, ideas, or general feedback.
Chain these steps:
postmortem-analysis skill to structure the documentroot-cause-analysis skill to develop RCA sectionlog-analysis skill for accurate timeline with evidenceAfter completion, suggest: "Review this with the team and assign owners to action items."