Debug

SkillMonitoring & ops

Lets your agent diagnose problems in a coding session by checking logs, traces, and state.

Available today. Use it from your connected AI after setup.

No other account needed.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Debug skill

About this capability

Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction

What this skill tells your AI

The instructions your AI receives, as published by yeachan-heo/oh-my-claudecode in skills/debug/SKILL.md and read by ahel’s review.

Use this skill when the user wants help diagnosing a current OMC/Claude-Code session problem, workflow breakage, or confusing runtime behavior.

Find the real failure signal quickly and explain the next corrective step.

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.

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.

Advanced