Communitygithub.com

验证

确保变更真正生效后再声称完成。

验证 是什么?

该技能确保开发者在对特性、修复或重构宣布完成之前,能够获得切实的证据。它提供了一套系统化的验证流程:首先确定必须证明的精确行为,优先使用现有测试,缺失覆盖时运行最窄的直接验证命令,最后在自动化不足时描述手动验证步骤并收集可观察证据。支持测试、类型检查、构建、直接命令验证和手动验证等多种验证方式。核心原则是禁止在没有证据的情况下声称变更完成,要求清晰报告失败信息,并在无法验证时明确说明而非硬撑。最终输出格式包括验证内容、执行的命令/测试、通过项和失败或未验证项。

兼容平台~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

相关技能