// Send a bug or failing test to Claude Code for root-cause analysis and fix. Use when you've hit an error you can't trace, a test is failing for unclear reasons, or a behavior is wrong and the cause is deep in the codebase.
| name | claude-debug |
| description | Send a bug or failing test to Claude Code for root-cause analysis and fix. Use when you've hit an error you can't trace, a test is failing for unclear reasons, or a behavior is wrong and the cause is deep in the codebase. |
| version | 0.2.0 |
Delegate a debugging session to Claude Code — Claude traces the root cause and applies a fix.
mcp__claude-code__claude_code:
prompt: |
Debug the following issue and fix it.
SYMPTOM: {error message, failing test name, or wrong behavior description}
ERROR OUTPUT:
```
{paste stack trace or test output here}
```
REPRODUCTION STEPS: {how to reproduce — command to run, inputs, etc.}
WHAT I TRIED: {optional — what you already ruled out}
Instructions:
1. Read the source files involved in the reported code flow
2. Identify the root cause (not just where it crashes — why)
3. Apply a minimal, correct fix
4. Run the failing test/command to confirm the fix works
5. Check for regressions in related tests
6. Report: root cause, fix applied, verification result
PROVENANCE NOTE: The code being debugged was written by OpenAI Codex. Evaluate
with full rigor — do not assume Codex's code is correct anywhere adjacent to the
reported bug. Check surrounding logic independently.
cwd: {project working directory}
effort: high
Save the returned session_id as {debug_session_id}.
If Claude identified the root cause but couldn't fix it cleanly, or found related issues:
mcp__claude-code__claude_code_reply:
session_id: {debug_session_id}
prompt: "You identified the root cause in parseConfig(). Also check validateConfig() — it has a similar pattern."
Report to the user:
effort: high is important for non-obvious bugs; shallow effort stops at symptomspermissionMode defaults to default (allows writes) — Claude will apply the fix directlyclaude-plan — use before debugging to sketch a diagnosis strategy for complex, multi-file issuesclaude-implement — use after root cause is identified to apply a larger fix or refactor$audit-fix — use when the bug is a pattern across many files and needs a full audit→fix cycleFull audit→fix→verify cycle: Claude audits, Codex fixes, Claude verifies. Repeats up to 3 rounds until all issues are resolved or the user stops. Claude does all code reading and judgment; Codex does all file editing.
Diagnose the cc-suite setup in the current project. Runs the full health check, explains every issue, and fixes what can be fixed automatically. Skill counterpart to /cc-suite:diagnose.
Initialize cc-suite for the current project — sets up the AGENTS.md bridge, registers Codex and Claude MCP servers, and generates a .cc-suite.md config. Skill counterpart to /cc-suite:init.
Non-interactive re-run of all cc-suite bridge and registration scripts. No questions asked — idempotent escalation step after the diagnose skill finds issues it could not fix. Skill counterpart to /cc-suite:repair.
Use when writing, reviewing, or naming any cc-suite artifact — pick the canonical noun or verb from this registry rather than coining a synonym. Loaded by NLPM's scorer and checker when R51 is enabled in .claude/nlpm.local.md.
Use when creating, editing, or reviewing a cc-suite advisor agent (a value-over-rules persona under `.cc-suite/agents/`). Covers system-prompt phrasing, model choice, tool restrictions, working-dir scoping, budget/turn limits, and the file format. Use proactively whenever the user asks to "add an agent", "make an advisor", "write a reviewer", or edits anything under `.cc-suite/agents/`.