Generates blameless postmortems with root-cause analysis for software incidents.
npx skills add https://github.com/thoreinstein/opencode-config --skill postmortem
Please help me install this Agent Skill. Skill: postmortem Source: https://github.com/thoreinstein/opencode-config/tree/main/skill/postmortem Command: npx skills add https://github.com/thoreinstein/opencode-config --skill postmortem
This Skill automates the creation of blameless postmortems with root-cause analysis, reducing time-to-insight after incidents and strengthening organizational learning.
Use this skill to generate a blameless postmortem for incident reference "INCIDENT-XXXX" and publish it to Obsidian at the path Postmortems/YYYY-MM-DD-incident-title.md.
High-intent search queries and answers about installing and using this skill.
Automating blameless postmortem generation involves coordinating external research, codebase exploration, and code analysis to produce a structured root-cause analysis. This process builds an incident document focused on organizational learning and prevention.
Writing a five whys root-cause analysis into Obsidian requires appending the synthesized RCA document using an auto-generated filename like YYYY-MM-DD-incident-title.md. The output includes a wiki-link back to the original incident reference.
Conducting root-cause analysis across multiple codebases is best handled by guiding parallel research tracks. This approach simultaneously surfaces external research, codebase exploration, and code analysis to identify contributing factors and durable fixes.
This incident management approach requires an Obsidian vault configured to accept appended content. It writes the final postmortem document to a specified path within the vault, ensuring structured documentation aligned with organizational standards.
Generating a structured postmortem document from an incident reference ID like INCIDENT-XXXX is fully supported. The system uses the reference to coordinate research tracks and publishes the blameless postmortem directly to your Obsidian vault.
Automated postmortem templates should not be used when an incident lacks sufficient codebase context or external research data. Without these inputs, the parallel research tracks cannot effectively synthesize an accurate five whys root-cause analysis.
thoreinsteinGenerate prioritized triage checklists for production incidents and log findings to Obsidian.
as4584Generate blameless postmortem documents with root cause analysis and action items.
winsorllcSearch, list, create, read, append, and link Obsidian markdown notes.
wyre-technologyManage Rootly incidents across creation, triage, update, and resolution workflows.
