Skip to content
Agent Orchestration
Skill

/debug

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

Boost this skill
@yeachan-heoyeachan-heo@yeachan-heo
From plugin
oh-my-claudecode
39k39 skills21 agents21 commands11 hooks
+1
Install
$ npx -y skills add Yeachan-Heo/oh-my-claudecode --skill debug --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/debug

Context preview

The summary Claude sees to decide when to auto-load this skill.

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

SKILL.md

debug.SKILL.md
name: debug
description: Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction

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
Read it on GitHub ↗
Ships withoh-my-claudecode

For Codex users: Check out oh-my-codex — the same orchestration experience for OpenAI Codex CLI. Liked OmC but found it a bit overkill? Try gajae-code.

Get the whole plugin
Stats
TypeScriptNodeBashREST APILinux
+7 tags
GitGitHubMarkdownAnthropicOpenAIGeminiMCP
39,110
Stars
3,501
Forks
Active
Maintenance
TypeScript
Language
MIT
License
1d ago
Last commit
8mo ago
Created
13d ago
Added

Repo: Yeachan-Heo/oh-my-claudecode

In this plugin
39 skills21 agents21 commands11 hooks1 MCP
See everything inside

Other skills on oh-my-claudecode.

See all 39 skills in oh-my-claudecode