Document root causes and corrective actions for resolved incidents.
npx skills add https://github.com/RonanCodes/ronan-skills --skill post-mortem-ronancodes
Please help me install this Agent Skill. Skill: post-mortem Source: https://github.com/RonanCodes/ronan-skills/tree/main/skills/post-mortem Command: npx skills add https://github.com/RonanCodes/ronan-skills --skill post-mortem-ronancodes
Document how to effectively capture and share learnings from bugs or incidents to prevent recurrence.
Describe the incident, capture root cause, actions taken, and lessons learned, and save as a timestamped markdown file.
High-intent search queries and answers about installing and using this skill.
A post-mortem is a structured incident report documenting root causes and corrective actions after a resolved bug or outage. You need to write one during post-incident reviews to distill lessons learned and prevent recurrence across engineering teams.
To write a post-mortem report, describe the incident symptom, capture the root cause, list actions taken, and outline lessons learned. Save the completed report as a timestamped markdown file to ensure consistent documentation across teams.
Yes, a post-mortem template requires a clear root-cause statement. Template-driven guidance ensures you capture the symptom, root cause, actions taken, and lessons learned sections consistently for every incident.
The best way to document root cause and lessons learned for bug analysis is using a structured post-mortem template. This ensures you capture the symptom, root cause, actions taken, and lessons learned to drive improvements and knowledge-sharing.
Yes, you can use post-mortem documentation for knowledge-sharing across engineering teams. By capturing root causes and lessons learned in a structured template, teams can review incident reports and drive improvements to prevent future outages.
Template-driven post-mortems require a clear root-cause statement and concise lessons-learned section to be effective. Without a structured template, capturing symptoms and corrective actions consistently across different incidents and teams becomes difficult.
TheBushidoCollectiveManage production incidents across detection, triage, mitigation, and postmortem workflows.
wuyyyyyouCreate a Docs post-mortem, schedule a Calendar review, and notify teams in Chat.
mtsatryanCoordinate incident response and communications across detection, declaration, resolution, and post-mortem learning.
timequityCreate blameless postmortems documenting root-cause analyses with structured markdown templates.
