skills.rest
chavangorakh1999
chavangorakh1999COMMUNITY
Explore all skills by this author →
Website𝕏@grc_jrGitHub

root-cause-analysis

Analyzes the root cause of incidents using structured methods like 5 Whys and Fishbone diagrams.

1|Updated Mar 6, 2026
Search Tags:#debugging#problem solving#incident response#postmortem#5 Whys#RCA
One-click install
npx skills add https://github.com/chavangorakh1999/sde-skills --skill root-cause-analysis-chavangorakh1999
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: root-cause-analysis
Source: https://github.com/chavangorakh1999/sde-skills/tree/main/sde-debugging/skills/root-cause-analysis
Command: npx skills add https://github.com/chavangorakh1999/sde-skills --skill root-cause-analysis-chavangorakh1999

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you move beyond surface-level symptoms to identify the fundamental, systemic issues causing recurring problems or incidents, ensuring lasting solutions.

Core Features & Use Cases

  • Structured Problem Solving: Employs methodologies like 5 Whys, Fishbone diagrams, and Fault Tree Analysis.
  • Actionable Insights: Guides you to define concrete, preventive actions rather than temporary fixes.
  • Use Case: When a service outage occurs, use this Skill to systematically trace the cause from the initial symptom (e.g., "users can't log in") down to a fixable root (e.g., "missing automated safeguards in the testing and review process").

Quick Start

Analyze the root cause of the recent login issue using the 5 Whys method.

Frequently Asked Questions about root-cause-analysis

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

FAQPage Schema
How do I perform a root cause analysis for an incident using the 5 Whys method?▼

Perform root cause analysis by applying the 5 Whys method to iteratively ask why an incident occurred, tracing symptoms down to a systemic issue. This process identifies fundamental problems rather than stopping at surface-level symptoms.

When should I use a Fishbone diagram instead of Fault Tree Analysis for problem solving?▼

Use a Fishbone diagram for problem solving when exploring multiple potential causes across process, technology, and people factors. Fault Tree Analysis is better suited for mapping logical chains of failures within complex incidents.

Can I use this to define corrective and preventive actions after a service outage?▼

Yes, you can use this to define corrective and preventive actions after a service outage. It analyzes systemic issues found during incident response and guides the creation of concrete fixes to prevent recurrence.

What is the best way to structure a postmortem for recurring incidents?▼

The best way to structure a postmortem for recurring incidents is to use structured RCA methodologies like 5 Whys and Fishbone diagrams. This identifies systemic issues across process, technology, and people factors to ensure lasting solutions.

Does root cause analysis work for both process and technology failures?▼

Yes, root cause analysis works for both process and technology failures. It evaluates people, process, and technology factors simultaneously to find systemic issues and guide preventive actions rather than temporary fixes.

Related Skills

Explore More Software Engineering Skills→
tclemtclem
11

incident-postmortem

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

Community
Intermediate
edwardmonteiroedwardmonteiro

optimization.postmortem

Generate standardized postmortem documents with root-cause analysis and corrective actions.

Community
Basic
AnastasiyaWAnastasiyaW
140

observability-monitoring

Audit Prometheus alert rules using the RED method.

Community
Advanced
nbarthelemynbarthelemy

pattern-observer

Observe development patterns and auto-create automation opportunities after recurrent occurrences.

Community
Advanced