Debug
Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction
Specification
- Skill ID
- yeachan-heo/oh-my-claudecode/debug
- Publisher
- yeachan-heo
- Repository
- oh-my-claudecode
- Installs
- 0
- Files
- 1
- Synced
- Sep 23, 2026
How to use it
Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.
yeachan-heo/oh-my-claudecode/debugInstalls these files- SKILL.md
What this skill tells the agent
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
- Read the user’s issue description carefully.
- Inspect the most relevant local evidence first:
- trace tools
- state tools
- notepad / project memory when relevant
- failing tests or commands
- Reproduce the issue narrowly if possible.
- Distinguish symptoms from root cause.
- 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.
Output
- Observed failure
- Root-cause hypothesis
- Evidence for that hypothesis
- Smallest next action
More from yeachan-heo
Use this skill in a project
Open any RiverX project, search the Skills panel for yeachan-heo/oh-my-claudecode/debug, and install it in one click.