Communitygithub.com

偵錯

診斷目前 OMC 工作階段或儲存庫狀態,使用日誌、追蹤、狀態和聚焦重現。

偵錯 是什麼?

此技能專為診斷 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

相關技能