debug · yeachan-heo — Claude Code skill: what it does, how to install
Diagnoses broken OMC sessions, workflow failures, and repo state issues using traces and targeted reproduction.
npx skills add Yeachan-Heo/oh-my-claudecode --skill debug -a claude-codeWhat debug does
The skill tracks down runtime failures and orchestration issues in oh-my-claudecode sessions. It inspects local evidence first: trace logs, state tools, project memory, and failing test commands, prioritizing facts over assumptions.
Broad rewrites before isolating the failure are explicitly forbidden. Temporary diagnostic prints get marked with a [DEBUG-<4hex>] tag. Cleanup needs just one grep. Sensitive data and credentials are scrubbed from logs before leaving the session.
The resulting report outlines the observed failure, a root-cause hypothesis backed by evidence, and the smallest corrective step. If an architectural seam is broken, the skill points directly to refit or architecture-survey.
What it helps with
- isolate orchestration breakdowns across hooks and agents
- separate surface symptoms from the root cause
- clean up temporary debug output using grep tags
- redact credentials from logs before sharing
Example prompts for the agent
- Diagnose why the agent hook broke during this session
- Find the root cause of this test failure using session traces
- Investigate confusing runtime behavior without rewriting existing code
How to install debug
1Skills CLI (Vercel)
npx skills add Yeachan-Heo/oh-my-claudecode --skill debug -a claude-code2Manually: put the files in place
~/.claude/skills/debug/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/debug/
1Skills CLI (Vercel)
npx skills add Yeachan-Heo/oh-my-claudecode --skill debug -a codex2Manually: put the files in place
.agents/skills/debug/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Yeachan-Heo/oh-my-claudecode --skill debug -a cursor2Manually: put the files in place
.cursor/skills/debug/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Yeachan-Heo/oh-my-claudecode debug2Manually: put the files in place
.github/skills/debug/SKILL.md1Skills CLI (Vercel)
npx skills add Yeachan-Heo/oh-my-claudecode --skill debug -a gemini-cli2Platform CLI
gemini skills install https://github.com/Yeachan-Heo/oh-my-claudecode --path skills/debugManually: put the files in place
.devin/skills/debug/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Yeachan-Heo/oh-my-claudecode --skill debug -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set26
The whole set →Other versions of debug
Similar
Questions about debug
How to install debug in Claude Code?
Run npx skills add Yeachan-Heo/oh-my-claudecode --skill debug -a claude-code in your terminal. You can also place it directly at ~/.claude/skills/debug/SKILL.md.
What does the debug skill do?
It analyzes traces, session state, and memory to uncover the real root cause of runtime errors, then recommends the smallest next fix.
How does the skill handle temporary log lines?
It tags temporary diagnostic output with [DEBUG-<4hex>], allowing you to clean up all temporary lines with a single grep command.
Source text
SKILL.md · MIT
--- name: debug description: Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction --- # Debug Use this skill when the user wants help diagnosing a current OMC/Claude-Code session problem, workflow breakage, or confusing runtime behavior. ## Goal Find the real failure signal quickly and explain the next corrective step. ## Workflow 1. Read the user’s issue description carefully. 2. Inspect the most relevant local evidence first: - trace tools - state tools - notepad / project memory when relevant - failing tests or commands 3. Reproduce the issue narrowly if possible. 4. Distinguish symptoms from root cause. 5. Recommend the smallest next fix or verification step. ## Rules - Prefer real evidence over guesses. - Use the trace/state surfaces when the issue involves orchestration, hooks, or agent flow. - If the issue is actually a product/runtime bug rather than app code, say so plainly. - Do not prescribe broad rewrites before isolating the failure. - Tag temporary debug output `[DEBUG-<4hex>]`; cleanup is then a single grep. - Redact secrets from logs and traces before they leave the session. - If the failure traces to a missing or wrong seam, say so as the finding and point at `refit` or `architecture-survey` — the environment lesson outlives the fix. ## Output - Observed failure - Root-cause hypothesis - Evidence for that hypothesis - Smallest next action
© Yeachan-Heo · MIT · Yeachan-Heo/oh-my-claudecode