debug
Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction
来源信息
- 仓库
- Yeachan-Heo/oh-my-claudecode
- 最近来源活动
- 2026年4月1日 05:27
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 39,401
- 分支
- 3,524
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
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
在 GitHub 查看