Communitygithub.com

驗證

在聲明完成之前,確認變更確實有效。

驗證 是什麼?

這個技能確保開發者在聲明功能、修復或重構完成之前,能獲得實際的驗證證據,避免依賴模糊的「應該可以運作」的聲明。它支援主流開發環境與 AI 代理工具(如 Claude Code、Cursor),透過結構化工作流程引導使用者:1) 明確需要驗證的行為;2) 優先執行既有測試;3) 如果測試覆蓋不足,則執行最精確的直接驗證命令;4) 必要時描述人工驗證步驟並收集具體可觀察證據;5) 僅報告實際驗證的結果。驗證順序由既有測試、型別檢查/建置、狹義命令檢查,到人工或互動式驗證逐步進行。核心規則包括:不得無證據宣稱完成、清楚報告失敗、若無實際驗證途徑須明確說明,以及偏好簡潔的證據摘要而非雜亂的日誌。最終輸出應包含驗證內容、執行的命令/測試、通過項目以及失敗或未驗證項目,從而提供完整且可信的驗證報告。

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

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

驗證 是做什麼的?

當使用者希望確保功能、修復或重構確實有效時,請使用此技能。

目標

將模糊的「應該可以運作」的宣稱轉化為具體的證據。

工作流程

  1. 找出必須被證明的確切行為。
  2. 首先優先使用現有測試。
  3. 如果測試覆蓋不足,執行可用的最精確的直接驗證命令。
  4. 如果直接自動化不足,描述人工驗證步驟並收集具體可觀察的證據。
  5. 僅回報實際驗證過的內容。

驗證順序

  1. 現有測試
  2. 型別檢查 / 建置
  3. 狹義直接命令檢查
  4. 人工或互動式驗證

規則

  • 沒有證據,不得宣稱變更完成。
  • 如果檢查失敗,請清楚包含失敗內容。
  • 如果不存在實際的驗證途徑,請明確說明,而不是虛張聲勢。
  • 偏好簡潔的證據摘要,避免雜亂的日誌。

輸出

  • 驗證了什麼
  • 執行了哪些命令/測試
  • 通過了什麼
  • 什麼失敗或仍未驗證

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

debug

Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction

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

相關技能