incident-log-to-postmortem
Skill0 starsChanged 5 months agoMITView on GitHub
Use when summarizing incident logs, outage timelines, status updates, alerts, or team notes into a clear postmortem with impact, timeline, root-cause candidates, and follow-up actions.
In this repository19 other files it gives its agents.
- agent-handoff-briefSkill
- api-doc-to-tool-specSkill
- architecture-rfc-reviewSkill
- bug-report-to-reproSkill
- changelog-to-upgrade-planSkill
- competitive-research-briefSkill
- customer-call-to-prdSkill
- database-migration-risk-reviewSkill
- dependency-upgrade-risk-reviewSkill
- messy-notes-to-decision-logSkill
- privacy-data-flow-mapSkill
- prompt-to-eval-rubricSkill
- repo-launch-readiness-reviewSkill
- roadmap-to-release-planSkill
- security-review-checklistSkill
- support-ticket-to-evalSkill
- telemetry-to-product-insightsSkill
- tool-permission-auditSkill
- workflow-automation-scoutSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Use when incident evidence needs to become a postmortem draft or follow-up action list.
- Distinctive: line 15
Do not use when the incident is still active and the priority is live mitigation.
- Distinctive: line 49
Follow-up actions have owners or owner placeholders.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Incident Log To Postmortem
Purpose
Turn scattered incident material into a readable postmortem draft without overstating the root cause.
Fit
- Use when incident evidence needs to become a postmortem draft or follow-up action list.
- Do not use when the incident is still active and the priority is live mitigation.
Inputs
- Incident timeline, alerts, logs, status updates, or chat notes.
- Impact details, affected users, duration, and remediation steps if available.
- Current uncertainty or disputed explanations.
Workflow
- Build a chronological timeline from earliest signal to recovery.
- Separate confirmed facts from hypotheses.
- Identify impact, detection, mitigation, recovery, and prevention gaps.
- List root-cause candidates with evidence and confidence.
- Convert prevention ideas into owner-ready follow-up actions.
Output
Produce Markdown with:
- Incident Summary
- Impact
- Timeline
- Root-Cause Candidates
- What Worked
- What Failed
- Follow-Up Actions
- Open Questions
Validation
- Timeline entries include timestamps or clear ordering.
- Root cause is not claimed when only candidates exist.
- Impact is scoped to evidence.
- Follow-up actions have owners or owner placeholders.
- Blame language is removed; system factors are emphasized.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.