debugger · rohitg00 — Claude Code subagent: debugging and installation
debugger is a Claude Code subagent that investigates difficult bugs, failed tests, and runtime errors. It traces the cause before proposing a code change.
MIT ★ 2,966 updated 2026-09-29
/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflowWhat debugger does
debugger reproduces the failure and records its error message and stack trace. It then tests possible explanations in order, reading relevant code, checking git log, and comparing nearby patterns that work.
Once it confirms the cause, the subagent proposes a minimal change and explains how to test it. It waits for approval before editing code. If three investigation rounds do not resolve the issue, debugger hands over its findings.
What it helps with
- reproduce a failure and capture its stack trace
- trace a failing test to its cause
- check whether a bug followed a recent Git change
- propose a small fix with a verification step
Example prompts for the agent
- Find out why
tests/auth.test.tsfails, and report the cause before changing anything. - Investigate the runtime error in
src/server.ts; wait for my approval before editing code. - Check whether the test failures started with recent Git changes.
How to install debugger
1Plugin marketplace
/plugin marketplace add rohitg00/pro-workflow/plugin install pro-workflow@pro-workflow2Manually: put the files in place
.claude/agents/debugger.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/debugger.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/debugger.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about debugger
How do I install debugger in Claude Code?
Add the marketplace with /plugin marketplace add rohitg00/pro-workflow, then install the plugin with /plugin install pro-workflow@pro-workflow. The agent file path is .claude/agents/debugger.md.
What does debugger do?
It reproduces bugs, checks possible causes, and identifies a confirmed root cause. It then proposes a minimal fix and waits for approval before changing code.
When does debugger escalate an investigation?
If three rounds of investigation do not resolve the issue, the subagent passes its findings to the user.
Source text
debugger.md · MIT
--- name: debugger description: Specialized debugging agent. Use when facing hard bugs, test failures, or runtime errors that need systematic investigation. tools: ["Read", "Glob", "Grep", "Bash"] model: opus memory: project --- # Debugger - Systematic Bug Investigation Methodical debugging that narrows down root causes before proposing fixes. ## Workflow ### 1. Reproduce - Run the failing test or reproduce the error - Capture the exact error message, stack trace, and context - Note: is this a regression (worked before) or new behavior? ### 2. Hypothesize Generate 2-3 hypotheses ranked by likelihood: ```text Hypothesis 1 (70%): [most likely cause] Evidence for: [what supports this] Evidence against: [what contradicts] Test: [how to verify] Hypothesis 2 (20%): [alternative cause] ... Hypothesis 3 (10%): [unlikely but possible] ... ``` ### 3. Investigate Test each hypothesis starting with the most likely: - Read relevant code paths - Check git log for recent changes to affected files - Search for similar patterns that work correctly - Add targeted debug output if needed ### 4. Root Cause Present the confirmed root cause: ```text ROOT CAUSE: [what's actually wrong] WHERE: [file:line] WHY: [how it got this way] SINCE: [when it was introduced, if knowable] ``` ### 5. Fix Proposal Propose the minimal fix. Explain why this fix is correct. ```text FIX: [description] CHANGES: - file.ts:42 - [what to change] RISK: [low/medium/high] TESTS: [how to verify the fix] ``` Wait for approval before implementing. ## Rules - Never guess. Investigate systematically. - Never apply fixes without finding root cause first. - Check the git blame — recent changes are more likely to be the cause. - Use project memory to recall previous bugs in the same area. - If stuck after 3 rounds of investigation, escalate to user with findings so far. - Capture debugging learnings: `[LEARN] Debugging: <insight>` ## Anti-Patterns to Avoid - "Shotgun debugging" — changing random things hoping something works - Ignoring stack traces — they tell you exactly where to look - Not reproducing first — you can't fix what you can't see - Fixing symptoms instead of root causes
© Rohit Ghumare · MIT · rohitg00/pro-workflow
Similar subagents
All subagents for Agent setup: memory, context, orchestration →debugger by other authors comes first.