skills.rest
kabaka
kabakaCOMMUNITY
Explore all skills by this author →
GitHub

root-cause-analysis-workflow

Document root causes of defects through a structured debugging workflow.

Updated Sep 6, 2025
Search Tags:#debugging#documentation#investigation#root-cause-analysis#issue-triage#rca
One-click install
npx skills add https://github.com/kabaka/oscar-export-analyzer --skill root-cause-analysis-workflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: root-cause-analysis-workflow
Source: https://github.com/kabaka/oscar-export-analyzer/tree/main/.github/skills/root-cause-analysis-workflow
Command: npx skills add https://github.com/kabaka/oscar-export-analyzer --skill root-cause-analysis-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow provides a repeatable, evidence-based approach to debugging and root-cause analysis, helping teams identify underlying causes rather than chasing symptoms.

Core Features & Use Cases

  • Evidence-driven investigation: Collect observations, reproduce steps, and gather logs to build a reliable knowledge base.
  • Hypothesis-driven testing: Form 3–5 testable hypotheses and design minimal, deterministic tests to validate or invalidate them.
  • Documentation discipline: Systematically record the investigation process, decisions, and rationales to prevent regression and enable knowledge transfer.
  • Use Case: When a bug reappears across environments, use this workflow to isolate the root cause and craft a robust fix with an auditable trail.

Quick Start

Begin by collecting evidence, list hypotheses, and design test steps before attempting a fix.

Frequently Asked Questions about root-cause-analysis-workflow

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

FAQPage Schema
What is a structured root cause analysis workflow for debugging?▼

A structured root cause analysis workflow systematically identifies defect origins through evidence collection, hypothesis formation, and deterministic testing to resolve underlying issues instead of chasing symptoms.

How do I document a bug investigation to prevent future regressions?▼

Document the bug investigation by systematically recording evidence, test steps, decisions, and rationales throughout the debugging process to create an auditable trail and enable knowledge transfer.

How do I find the root cause of a defect that reappears across different environments?▼

Isolate the root cause by collecting observations and logs to form 3-5 testable hypotheses, then design minimal deterministic tests to validate or invalidate each hypothesis before applying a fix.

Does this root cause analysis approach work for issue triage across different project teams?▼

Yes, this root cause analysis approach applies to bug investigations across environments, projects, and teams, guiding evidence collection and hypothesis testing to ensure consistent issue triage.

What's the best way to start a root cause analysis when a bug is reported?▼

The best way to start a root cause analysis is by collecting evidence, listing observations, and designing test steps to form hypotheses before attempting any code fix.

Related Skills

Explore More Software Engineering Skills→
rahmanayonrahmanayon

investigate

Plan root-cause investigations across investigate, analyze, hypothesize, and implement phases.

Community
Advanced
StudentCristianStudentCristian

nw-bugfix

Coordinate root-cause analysis, user validation, and regression testing for defect resolution.

Community
Advanced
RealEmmettSRealEmmettS

bug-triage

Guide bug triage with reproducibility, evidence gathering, and structured reporting.

Community
Advanced
icartshicartsh
4

code-analyze

Analyze .NET solutions for code quality, security, and dependency issues.

Community
Advanced