Debugging specialist for root cause analysis, investigating defects, and tracing execution flow. Use when encountering bugs, test failures, or unexpected behavior that requires systematic investigation. For example: tracing a null pointer exception, analyzing intermittent test fa
How to install debugger?
josstei/maestro-orchestrate/debugger
$curl -o .claude/agents/debugger.md https://raw.githubusercontent.com/josstei/maestro-orchestrate/HEAD/agents/debugger.mdInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Install debugger by running `curl -o .claude/agents/debugger.md https://raw.githubusercontent.com/josstei/maestro-orchestrate/HEAD/agents/debugger.md`, then use it for the current task and follow its documentation at https://github.com/josstei/maestro-orchestrate.
agents/debugger.md
| 1 | Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["debugger"])` to read the full methodology at delegation time. |
Related
6 picksType
- debuggerRoot-cause analysis, regression isolation, stack trace analysis, build/compilation error resolutionJul 2026
- exploreCodebase search specialist for finding files and code patternsJul 2026
- tracerEvidence-driven causal tracing with competing hypotheses, evidence for/against, uncertainty tracking, and next-probe recommendationsJul 2026
- performance-analystThe Performance Analyst profiles game performance, identifies bottlenecks, recommends optimizations, and tracks performance metrics over time. Use this agent for performance profiling, memory…May 2026
- debuggerUse this agent when encountering errors, test failures, unexpected behavior, or any issues that require root cause analysis. The agent should be invoked proactively whenever debugging is needed.Jul 2026
- explorerRead-only code exploration sub-agent. Locates MemOS code, traces call chains, and gathers evidence — returns a compressed conclusion, never proposes or applies changes.Jul 2026
