Debug
- 301 installs
- 38.3k repo stars
- Updated August 4, 2026
- yeachan-heo/oh-my-claudecode
debug is an oh-my-claudecode skill that runs a structured five-step diagnostic workflow—analyze, gather evidence, reproduce, identify root cause, and recommend minimal corrective action—for OMC or Claude Code session and
About
debug from oh-my-claudecode helps developers diagnose current OMC or Claude Code session problems, workflow breakage, and confusing runtime behavior. The skill follows five steps: read the issue, inspect local evidence from trace tools, state tools, notepad or project memory, and failing tests or commands, reproduce narrowly, separate symptoms from root cause, and recommend the smallest corrective action. Use debug when agents loop, hooks misfire, traces show silent failures, or project memory disagrees with runtime state. It prioritizes local artifacts—logs, traces, state dumps—over speculative refactors so engineers get a concrete next fix fast.
- Structured five-step diagnostic: analyze, evidence, reproduce, root cause, remediate
- Inspects trace tools, state info, project memory, and test failures
- Distinguishes between symptoms and underlying root causes
- Recommends minimal corrective action to avoid over-engineering
- Designed for diagnosing Claude Code session and workflow issues
Debug by the numbers
- 301 all-time installs (skills.sh)
- +9 installs in the week ending Jul 27, 2026 (Skillselion tracking)
- Ranked #136 of 596 Debugging skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/yeachan-heo/oh-my-claudecode --skill debugAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 301 |
|---|---|
| repo stars | ★ 38.3k |
| Last updated | August 4, 2026 |
| Repository | yeachan-heo/oh-my-claudecode ↗ |
How do you debug a broken Claude Code session?
Run a structured five-step diagnostic workflow to find the real failure signal fast: analyze, gather evidence, reproduce, identify root cause, and recommend minimal corrective action.
Who is it for?
Claude Code developers using oh-my-claudecode who need structured diagnosis of session, hook, or workflow runtime failures.
Skip if: Greenfield feature implementation or production SRE incidents on servers without local OMC traces and session state.
When should I use this skill?
An OMC or Claude Code session misbehaves, workflows break, or runtime traces and state need structured root-cause analysis.
What you get
Root-cause analysis, reproduction steps, inspected trace/state evidence, and a minimal corrective action recommendation.
- root-cause report
- reproduction steps
- fix recommendation
By the numbers
- Implements a five-step diagnostic workflow for OMC and Claude Code failures
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
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.
Output
- Observed failure
- Root-cause hypothesis
- Evidence for that hypothesis
- Smallest next action
Related skills
Azure DiagnosticsSystematically diagnose and resolve production issues on Microsoft Azure using official Microsoft guidance.495k1.3kAzure MessagingQuickly diagnose and fix connection, authentication, and message-processing failures when using Azure Event Hubs or Service Bus SDKs.483k1.3k
Diagnosing BugsGet a systematic, step-by-step process that surfaces the real root cause instead of guessing at bugs.291k200k
Use My BrowserWhen their agent task requires access to the live browser session, rendered DOM state, authenticated dashboards, localhost apps, or DevTools-selected elements instea269k71
Systematic DebuggingFollow a repeatable four-phase process that forces root-cause discovery before any code changes.210k265k
Safe DebugGet conservative, non-destructive diagnosis of deep learning and agent errors before any code changes are made.185k512FAQ
What evidence does the debug skill inspect first?
The debug skill inspects OMC trace tools, state tools, notepad or project memory, and failing tests or commands. It gathers local evidence before recommending the smallest corrective action.
How many steps are in the debug workflow?
The debug skill uses five steps: analyze the issue, gather evidence, reproduce narrowly, distinguish symptoms from root cause, and recommend minimal corrective action for OMC or Claude Code failures.