Debug

When your OMC session is acting weird or a workflow suddenly breaks, this gives you a structured way to actually figure out why instead of guessing. It walks through checking traces, state tools, and logs in order, helps you reproduce the problem narrowly, and separates symptoms from root cause before suggesting a fix. The real value is in how it forces you to look at evidence first rather than rewriting everything. It will also tell you plainly if you've hit an actual product bug rather than something in your code. Think of it as a diagnostic checklist that keeps you from spiraling when Claude Code itself seems confused.

skills.sh installs: 683
GitHub stars: 40.7K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add yeachan-heo/oh-my-claudecode --skill debug --agent claude-code

Installs into .claude/skills of the current project.

Files

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.