incident-postmortem

Collect incident data, logs, and metrics into structured postmortem reports.

11|Updated Sep 6, 2011

Search Tags:#root cause #incident response #telemetry #postmortem #incident

Ready to run

npx skills add https://github.com/tclem/dotfiles --skill incident-postmortem-tclem

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: incident-postmortem
Source: https://github.com/tclem/dotfiles/tree/main/copilot/skills/incident-postmortem
Command: npx skills add https://github.com/tclem/dotfiles --skill incident-postmortem-tclem

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill facilitates the systematic assembly, updating, and review of detailed, evidence-backed incident postmortems to enhance organizational learning and response quality.

Core Features & Use Cases

Incident Evidence Gathering: Collects data from issues, logs, metrics, and alerts to build a comprehensive incident record.
Structured Report Generation: Creates standardized postmortem templates including impact, timeline, cause analysis, and repair items.
Use Case: A DevOps team analyzing a service outage can use this skill to collate relevant telemetry, draft the root cause analysis, and document corrective actions for stakeholder review.

Quick Start

Tell the AI to assemble an incident postmortem report for the recent service disruption.

Frequently Asked Questions about incident-postmortem

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

FAQPage Schema

How do I automate incident postmortem report generation from logs and metrics?▼

Generating a blameless postmortem report requires collating incident data, logs, and metrics into a standardized template. This skill automates that collection to document impact, timeline, and repair items.

What is a blameless postmortem and how does it improve incident response?▼

A blameless postmortem is a structured incident analysis focusing on systemic root causes rather than individual errors. It enhances continuous improvement by organizing telemetry and evidence into standardized reports for stakeholder review.

Can I use this to gather incident evidence from issue URLs and telemetry data?▼

Yes, you can gather incident evidence from issue URLs, logs, and metrics. The skill processes these input sources to build a comprehensive incident record that details the impact, timeline, and root cause.

What is the best way to structure a root cause analysis for a service outage?▼

The best way to structure a root cause analysis for a service outage is using a standardized postmortem template. This includes impact assessment, timeline reconstruction, cause analysis, and documented corrective repair items.

Do I need specific dependencies to create continuous improvement reports for incident analysis?▼

No specific dependencies are required to create continuous improvement reports for incident analysis. The skill operates independently to process input sources like issues, logs, and alert metrics into structured postmortem documentation.