claude-code-debugger

Run parallel domain assessment for complex debugging symptoms

Main claude-code-debugger entry. Dispatches to a subcommand based on your request, or lists options if unclear. Use `claude-code-debugger:<subcommand>` to target a specific action directly.

Deep iterative debugging: investigate root cause with causal tree analysis, fix, verify, score, critique — up to 5 iterations

Load full details for a specific incident or pattern from debugging memory.

Scan recent sessions for debugging incidents

Show debugging memory statistics

Search past bugs for similar issues before debugging

Submit feedback or report issues

Update claude-code-debugger to the latest version

Use this agent when the debugging symptom involves API endpoints, REST/GraphQL errors, request/response issues, authentication, rate limiting, or server-side route handlers. Examples - "500 error", "endpoint not found", "auth failed", "CORS error".

Use this agent when debugging requires multi-domain analysis, when the symptom is unclear about which domain is affected, or when you need to coordinate parallel assessments across database, frontend, API, and performance domains.

Use this agent when the debugging symptom involves database issues, queries, migrations, schema problems, Prisma errors, PostgreSQL, connection pooling, or data integrity. Examples - "slow query", "migration failed", "constraint error", "Prisma error", "connection timeout".

Use this agent to pressure-test a proposed fix before declaring a bug resolved. Challenges whether the fix addresses the root cause or just a symptom, checks for potential regressions, and verifies evidence exists for the claimed fix. Run after a fix is implemented but before declaring it done.

Use this agent when the debugging symptom involves React, hooks, rendering, UI components, state management, hydration errors, or client-side performance. Examples - "useEffect infinite loop", "component not rendering", "hydration mismatch", "state not updating".

Use this agent when the debugging symptom involves slowness, latency, timeouts, memory leaks, CPU usage, bottlenecks, or optimization needs. Examples - "app is slow", "memory keeps increasing", "timeout errors", "high CPU usage".

Use this agent when a debugging symptom needs deep causal analysis beyond surface-level diagnosis. Builds a causal tree (not a single chain) to explore multiple potential root causes in parallel. Flags when investigation reaches external/environmental boundaries or when internet research is needed. Examples - "why does this keep failing", "what's the real cause", "dig deeper into this error", "this fix didn't stick".

Use when debugging requires deep investigation beyond memory lookup — when the debugging-memory skill returns LIKELY_MATCH, WEAK_SIGNAL, or NO_MATCH, when a fix didn't hold, when the user explicitly asks for root cause analysis, deep investigation, or iterative debugging, or when you suspect the initial diagnosis is superficial. Not for known fixes or trivial issues.

This skill should be used when the user asks to "debug this", "fix this bug", "why is this failing", "investigate error", "getting an error", "exception thrown", "crash", "not working", "what's causing this", "root cause", "diagnose this issue", or describes any software bug or error. Also activates when spawning subagents for debugging tasks, using Task tool for bug investigation, or coordinating multiple agents on a debugging problem. Provides memory-first debugging workflow that checks past incidents before investigating.

This skill activates when the user asks to "add logging", "add tracing", "improve observability", "no logs", "can't see what's happening", "silent failure", "need visibility", "add instrumentation", "OpenTelemetry", "structured logging", "Jaeger", "set up monitoring", "add error tracking", or describes any lack of runtime visibility in their application. Generates stack-appropriate structured logging code with zero-dependency defaults and optional OTel integration.

1 hook across 1 event