Communitygithub.com

Ask

面向流程的顾问路由技能,通过 `omc ask` 调用 Claude、Codex、Gemini、Antigravity、Grok 或 Cursor,并保存结果为制品,无需手动构建 CLI 命令。

Ask 是什么?

Ask 是 OMC 的规范顾问路由技能。它允许用户通过统一的 `omc ask` 命令,将提示路由到本地的 Claude、Codex、Gemini、Antigravity、Grok 或 Cursor CLI,并将结果持久化为 Ask 制品。该技能的核心价值在于:用户无需手动构建不同 provider 的原始 CLI 命令,避免了因标志选择错误、版本不兼容等问题导致的调用失败。`omc ask` 会自动处理正确的标志选择、制品持久化和 provider 版本兼容性。支持 macOS/Linux 平台,其中 Antigravity CLI 在 Windows 上因已知限制会给出明确错误提示,建议 Windows 用户改用 Gemini。使用前需确保相应的本地 CLI 已安装并完成身份验证。

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

在你喜欢的 AI 中提问

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

文档

Ask 是做什么的?

使用 OMC 的规范顾问技能,将提示路由到本地的 Claude、Codex、Gemini、Antigravity、Grok 或 Cursor CLI,并将结果持久化为 Ask 制品。

用法

/oh-my-claudecode:ask <claude|codex|gemini|antigravity|grok|cursor> <问题或任务>

示例:

/oh-my-claudecode:ask codex "从安全角度审查此补丁"
/oh-my-claudecode:ask gemini "为此流程建议 UX 改进"
/oh-my-claudecode:ask antigravity "为此流程建议 UX 改进"
/oh-my-claudecode:ask claude "为 issue #123 起草实施计划"
/oh-my-claudecode:ask cursor "应用此实施计划"

路由

必需的执行路径 — 始终使用此命令:

omc ask {{参数}}

请勿手动构建原始 provider CLI 命令。 永远不要直接运行 codex、claude、gemini、agy、grok 或 cursor-agent 来满足此技能。omc ask 包装程序会自动处理正确的标志选择、制品持久化和 provider 版本兼容性。手动组装 provider CLI 标志将产生不正确或过时的调用。

要求

  • 所选本地 CLI 必须已安装并通过身份验证。
  • 使用相应的命令验证可用性:
claude --version
codex --version
gemini --version
agy --version
grok --version
cursor-agent --version
  • Antigravity CLI 安装(Gemini CLI 的 Google 后继者):按照官方 Antigravity 说明安装 agy 二进制文件(运行前检查任何安装程序)。验证:agy --version

    平台说明: omc ask antigravity 在 macOS/Linux 上受支持。在 Windows 上会给出明确的错误提示,因为 agy --print 将提示作为 argv 值(无法读取 stdin),并且已知存在上游 Windows -p 限制;在 Windows 上请使用 omc ask gemini。

  • Gemini CLI 仍受支持,适用于企业/API 密钥用例。

制品

omc ask 将制品写入:

.omc/artifacts/ask/<provider>-<slug>-<timestamp>.md

任务:{{参数}}

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-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

omc-doctor

Diagnose and fix oh-my-claudecode installation issues

相关技能