coding-debugger

Plugin coding-debugger in tyroneross/claude-code-debugger. Commands read from the repo's manifest — 2 days ago.

Skills (3)

• debug-loop

  Use for deep iterative debugging when memory lookup returns LIKELY_MATCH/WEAK_SIGNAL/NO_MATCH, a fix didn't hold, or the user asks for root cause analysis. Not for known fixes or trivial issues.

• debugging-memory

  Use when the user asks to "debug this", "fix this bug", "investigate error", "diagnose", "root cause", or reports a crash/exception/failure. Memory-first workflow checks past incidents before investigating.

• logging-tracer

  Use when the user asks to "add logging", "add tracing", "improve observability", "OpenTelemetry", "structured logging", or reports silent failures or no runtime visibility. Generates stack-appropriate logging with optional OTel.

Slash commands (9)

• /coding-debugger:assess

  Run parallel domain assessment for complex debugging symptoms

• /coding-debugger:coding-debugger

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

• /coding-debugger:debugger-agent

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

• /coding-debugger:debugger-detail

  Load full details for a specific Coding Debugger incident or pattern ID.

• /coding-debugger:debugger-scan

  Scan recent sessions for debugging incidents

• /coding-debugger:debugger-status

  Show debugging memory statistics

• /coding-debugger:debugger

  Search past bugs for similar issues before debugging

• /coding-debugger:feedback

  Submit feedback or report issues

• /coding-debugger:update

  Update Coding Debugger to the latest version

Subagents (7)

• api-assessor

  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".

• assessment-orchestrator

  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.

• database-assessor

  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".

• fix-critique

  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.

• frontend-assessor

  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".

• performance-assessor

  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".

• root-cause-investigator

  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.

MCP servers (1)

• coding-debugger

  runs: node ${CLAUDE_PLUGIN_ROOT}/dist/src/mcp/server.js

Hooks (1)

• Stop

  npx @tyroneross/claude-code-debugger mine --days 1 --store 2>/dev/null || true

Similar plugins