yeachan-heo/oh-my-claudecode

debug

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

First seen Apr 3, 2026

Installation

$ npx skills add yeachan-heo/oh-my-claudecode --skill debug

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from yeachan-heo/oh-my-claudecode · top by installs.

npx skills add yeachan-heo/oh-my-claudecode

Browse all from yeachan-heo/oh-my-claudecode

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 39.0K
License LICENSE
Default branch main
Open issues 2
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,135 B
  • docs SUMMARY.md 1,096 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 447 installs

SKILL.md

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

  1. Reproduce the issue narrowly if possible.
  2. Distinguish symptoms from root cause.
  3. 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