Draft a blameless root cause analysis from incident evidence into docs/rca/<slug>.md.
npx skills add https://github.com/friedbotstudio/baseline --skill rca-friedbotstudio
Please help me install this Agent Skill. Skill: rca Source: https://github.com/friedbotstudio/baseline/tree/main/.claude/skills/rca Command: npx skills add https://github.com/friedbotstudio/baseline --skill rca-friedbotstudio
This Skill helps you turn incidents, outages, and recurring test failures into a clear blameless root cause analysis that explains what happened, why it happened, and what should change next.
Ask the RCA skill to draft a postmortem from your incident evidence and it will write a completed analysis to docs/rca/<slug>.md.
High-intent search queries and answers about installing and using this skill.
To write a blameless postmortem after a production outage, you need an evidence-based timeline, quantified impact, a single-sentence root cause, linked references, and assigned action items with owners and due dates.
A blameless root cause analysis is a formal incident review document that explains why an outage or repeated test failure occurred without assigning personal blame, needed when your team requires a standalone artifact before a bugfix intake.
You create an incident review from logs and alerts by building an evidence-based narrative timeline, capturing the resolution taken, and generating action items with named owners and due dates written to a markdown file.
The best way to document recurring test failures for a bugfix intake is to draft a root cause analysis that captures the quantified impact, resolution taken, and action items with assigned owners and due dates.
Yes, you can use a root cause analysis for recurring flaky test failures, as the process captures the evidence-based timeline, quantified impact, and action items needed to formally review the incident and route a bugfix.
A complete incident review document should include an evidence-based timeline, quantified impact, a single-sentence root cause, linked references, what went well, and action items with assigned owners and due dates.
openeuler-mirrorGenerate structured root cause analysis reports from system logs and performance metrics.
Amazon-QuickGenerate a blameless incident postmortem report with timeline, impact, root cause, and action items.
JonathanMitchell1234Guide SRE practices for SLOs, incident management, and monitoring with Python examples.
patricio0312revGenerate comprehensive blameless postmortems from structured incident data.
