Communitygithub.com

调试

诊断当前 OMC 会话或仓库状态,利用日志、追踪、状态和有针对性的复现来解决问题。

调试 是什么?

该技能旨在帮助开发者或 AI 代理用户快速诊断当前 OMC 或 Claude-Code 会话中遇到的问题,例如工作流中断或运行时行为异常。它通过优先检查本地证据(如追踪工具、状态工具、项目记忆和失败的测试命令)来缩短故障排查周期。技能强调区分症状与根本原因,并推荐最小的修复或验证步骤,避免不必要的广泛重构。支持在任何使用 OMC/Claude-Code 代理的平台上运行,其工作流程包括仔细阅读问题描述、复现问题(若可能)以及输出观察到的故障、假设的根本原因、支持证据和下一步最小操作。

兼容平台✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/Yeachan-Heo/oh-my-claudecode/tree/main/skills/debug

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

调试 是做什么的?

当用户希望诊断当前 OMC/Claude-Code 会话问题、工作流中断或令人困惑的运行时行为时,使用此技能。

目标

快速找到真正的故障信号,并解释下一步的纠正措施。

工作流程

  1. 仔细阅读用户的问题描述。
  2. 首先检查最相关的本地证据:
    • 追踪工具
    • 状态工具
    • 相关时的便签/项目记忆
    • 失败的测试或命令
  3. 如果可能,窄范围地复现问题。
  4. 区分症状与根本原因。
  5. 推荐最小的下一步修复或验证步骤。

规则

  • 优先使用真实证据而非猜测。
  • 当问题涉及编排、钩子或代理流时,使用追踪/状态表面。
  • 如果问题实际上是产品/运行时错误而非应用代码,请直接说明。
  • 在隔离故障之前,不要建议进行大规模重写。

输出

  • 观察到的故障
  • 根本原因假设
  • 支持该假设的证据
  • 最小的下一步操作

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

agent-doc-discipline

Writing-time discipline for documents agents consume (the five surfaces, specs, tickets, .omc/skills/) — every rule checkable and carrying a why, steps before reference, one meaning in one home, no restating what the environment already says. Mandatory at drydock seed generation and the launch C5 sediment pass; opt-in for any other agent-facing doc edit. The companion of minimal-code-discipline: that one disciplines code, this one disciplines papers.

ai-slop-cleaner

Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode

ask

Process-first advisor routing for Claude, Codex, Gemini, Antigravity, Grok, or Cursor via `omc ask`, with artifact capture and no raw CLI assembly

ask-navigator

Shipyard

autopilot

Full autonomous execution from idea to working code

autoresearch

Stateful single-mission improvement loop with strict evaluator contract, markdown decision logs, and max-runtime stop behavior

cancel

Cancel any active OMC mode (autopilot, ralph, ultragoal, swarm, ultrapilot, pipeline, team) and clean up retired legacy state

configure-notifications

Configure notification integrations (Telegram, Discord, Slack) via natural language

deepinit

Deep codebase initialization with hierarchical AGENTS.md documentation

deep-interview

Socratic deep interview with mathematical ambiguity gating before explicit execution approval

drydock

Lay the keel of the shipyard harness in any repo — the 4-pillar shared environment (Context, Rules, Tools, Standards) across 5 surfaces (CLAUDE.md, skills, design-system, mcp/cli, shared context) so that every human and agent inherits the same design language and anyone can ship. Run once per repo; re-run with --check to audit drift.

execute

Carry an approved task through to working, verified code

external-context

Invoke parallel document-specialist agents for external web searches and documentation lookup

graph

Deterministic orchestration graph runtime - declarative DAG pipelines with journal-based crash recovery

harbor

Harbor intake for external work — the captain only handles unresolved decisions. Sweeps incoming issues and PRs, verifies every claim before disposition, reuses every decision already made, and hands the maintainer a docket whose pending items each carry one question with options, recommendation, impact and evidence. Agent-autonomous for facts and for actions covered by standing authorization; signed for every new judgment. Never merges.

hud

Configure HUD display options (layout, presets, display elements)

launch

Shipyard

loft

Loft the shape before cutting steel — answer a design question that prose cannot settle by building a throwaway artifact: a pure logic module in a clickable shell, or structurally different UI variants behind one route. The captain reacts to the artifact; the answer folds into the decision; the artifact never docks. Use when a design question stalls in words, when a navigator map carries a loft ticket, or when a spec discussion reaches

minimal-code-discipline

YAGNI-ladder coding discipline for writing changes — existence-first, reuse before writing, dependency ladder, shortest correct diff, with non-negotiables that must never be minimized away

omc-doctor

Diagnose and fix oh-my-claudecode installation issues

相关技能