# root_cause_debugger

The root_cause_debugger Claude Code subagent investigates failures using logs, traces, and repository context. It ranks plausible causes and lays out how to repair and verify the issue.

- subagent · `type=agent` · Claude Code, Codex, Cursor · ★ 776 repo stars
- Author: AgenticOrgLab
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/AgenticOrgLab/ExecOrchestra/tree/HEAD/execorchestra/Pool/resources/agents/root_cause_debugger.md
- Updated: 2026-11-12
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/agenticorglab-root-cause-debugger

## What it does

root_cause_debugger examines failure evidence alongside implementation, configuration, environment, and dependency details. It ranks a small set of testable explanations, weighs evidence for and against each, and separates the underlying cause from later effects.

Its Markdown diagnosis covers reproduction conditions, symptoms, the likely causal chain, a minimal repair, and verification with regression tests. When the available evidence cannot support a root-cause choice, it says so. To add it to Claude Code, place the agent file at `.claude/agents/root_cause_debugger.md`.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/agents/root_cause_debugger.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

### Codex

**Manually: put the files in place**
- File: `.codex/agents/root_cause_debugger.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/root_cause_debugger.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/AgenticOrgLab/ExecOrchestra/tree/HEAD/execorchestra/Pool/resources/agents/root_cause_debugger.md

## When to use it
- trace an error in logs or a stack trace to a likely cause
- separate the underlying fault from its downstream effects
- compare failure hypotheses with repository evidence
- plan a minimal fix and regression checks

## Example prompts
- Trace this failure through the logs and repository code, then outline how to verify the cause.
- Find the most likely reason this test fails and separate it from the resulting symptoms.
- Compare the observed error with the repository configuration and propose a minimal repair.

## Similar
- [root-cause-debugger](https://affpapa.org/en/nevibecode/agents/root-cause-debugger.md) — subagent · ★ 4719 repo stars
- [root-cause-tracing](https://affpapa.org/en/nevibecode/skills/root-cause-tracing.md) — skill · 1400 installs
- [om-root-cause](https://affpapa.org/en/nevibecode/skills/om-root-cause.md) — skill · 3700 installs
- [root-cause-analysis](https://affpapa.org/en/nevibecode/skills/root-cause-analysis.md) — skill · 940 installs
- [022-root-cause-analysis](https://affpapa.org/en/nevibecode/skills/022-root-cause-analysis.md) — skill · 144 installs

From the same set: [agenticorglab/execorchestra](https://affpapa.org/en/nevibecode/by/agenticorglab/execorchestra.md) — 24 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
