Back to Details

debug

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Debug

调试

Use this skill when the user wants help diagnosing a current OMC/Claude-Code session problem, workflow breakage, or confusing runtime behavior.
当用户需要帮助诊断当前OMC/Claude-Code会话问题、工作流中断或存在困惑的运行时行为时，使用此skill。

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.
  1. 仔细阅读用户的问题描述。
  2. 优先检查最相关的本地证据：
    • trace工具
    • state工具
    • 相关的记事本/项目记忆
    • 执行失败的测试或命令
  3. 尽可能小范围复现问题。
  4. 区分症状与根本原因。
  5. 推荐最小粒度的下一步修复或验证步骤。

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.
  • 优先采用真实证据而非猜测。
  • 当问题涉及编排、钩子或Agent流程时，使用trace/state面板。
  • 如果问题本质是产品/运行时bug而非应用代码问题，请明确说明。
  • 在定位故障前不要提议大范围重写代码。

Output

输出

  • Observed failure
  • Root-cause hypothesis
  • Evidence for that hypothesis
  • Smallest next action
  • 观察到的故障
  • 根因假设
  • 支撑该假设的证据
  • 最小粒度的下一步操作