Agent Skills › Yeachan-Heo/oh-my-claudecode › debug

debug

GitHub

用于诊断 OMC/Claude-Code 会话问题、工作流中断或运行时异常。通过检查日志、追踪和状态证据，区分症状与根因，推荐最小修复步骤。

skills/debug/SKILL.md Yeachan-Heo/oh-my-claudecode

诊断会话故障排查工作流中断分析运行时行为

npx skills add Yeachan-Heo/oh-my-claudecode --skill debug -g -y

More Options

Use without installing

npx skills use Yeachan-Heo/oh-my-claudecode@debug

指定 Agent (Claude Code)

npx skills add Yeachan-Heo/oh-my-claudecode --skill debug -a claude-code -g -y

安装 repo 全部 skill

npx skills add Yeachan-Heo/oh-my-claudecode --all -g -y

预览 repo 内 skill

npx skills add Yeachan-Heo/oh-my-claudecode --list

Frontmatter

{
    "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.

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.
Tag temporary debug output [DEBUG-<4hex>]; cleanup is then a single grep.
Redact secrets from logs and traces before they leave the session.
If the failure traces to a missing or wrong seam, say so as the finding and point at refit or architecture-survey — the environment lesson outlives the fix.

6688a30 Current 2026-10-19 08:27
新增关于输出调试标签格式（[DEBUG-<4hex>]）、清理调试输出、脱敏日志/追踪中的秘密信息，以及指向 refit 或 architecture-survey 的规则。
41a4c0f 2026-07-25 07:05