root-cause

Map root causes of bugs across code, data, and dependencies.

11|7|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/sean-m-cooper/ai_tools --skill root-cause-sean-m-cooper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: root-cause
Source: https://github.com/sean-m-cooper/ai_tools/tree/main/skills/root-cause
Command: npx skills add https://github.com/sean-m-cooper/ai_tools --skill root-cause-sean-m-cooper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically analyze bugs, failures, or unexpected behavior to identify root causes. Examines code, data, dependencies, and logs without proposing fixes, producing a structured analysis that surfaces assumptions, evidence, gaps, and the simplest path forward.

Core Features & Use Cases

  • Maps the problem across code, data, and dependencies to surface hidden causes.
  • Documents evidence, assumptions, and gaps, and ranks probable root causes by likelihood.
  • Produces a non-editable, thinking-only analysis to guide fixes without proposing code changes.

Quick Start

Begin by articulating a concise problem statement and gathering relevant logs and data to drive a thorough root-cause analysis.

Frequently Asked Questions about root-cause

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

FAQPage Schema
How do I perform a root-cause analysis for unexpected behavior across code and data flows?▼

Perform a root-cause analysis by articulating a concise problem statement and gathering logs to map causes across code, data, and dependencies without proposing code edits.

What is the best way to investigate bugs spanning third-party integrations and production environments?▼

Investigate bugs by mapping the problem across code paths and dependencies to surface hidden causes, documenting evidence, assumptions, and gaps to rank probable root causes.

How do I systematically document evidence and assumptions when debugging a failure?▼

Document evidence by systematically analyzing bugs to produce a structured analysis that maps problems across code and data, ranking probable root causes by likelihood.

Can I use this to diagnose production failures without modifying the codebase?▼

Yes, you can diagnose production failures non-invasively, as it produces a thinking-only analysis that guides fixes and surfaces probable root causes without proposing code changes.

Does this root-cause analysis approach work for both development and production environments?▼

Yes, this root-cause analysis works for both development and production environments, systematically examining code paths, data flows, and third-party integrations to identify root causes.

What are the limitations of a non-invasive root-cause analysis?▼

The limitation of this non-invasive root-cause analysis is that it produces a structured analysis to guide fixes but strictly does not propose or apply actual code changes.