Communitygithub.com

Ask:流程優先的顧問路由

透過 `omc ask` 將提示詞路由至 Claude、Codex、Gemini、Antigravity、Grok 或 Cursor,並將結果保存為構件,無需手動組裝 CLI 指令。

Ask:流程優先的顧問路由 是什麼?

Ask 技能是 Oh My Claude Code 框架中的核心顧問路由技能,旨在讓開發者無需記憶各 CLI 的繁瑣旗標,即可輕鬆將提示詞提交至多種 AI 代理平台。此技能支援 Claude、Codex、Gemini、Antigravity、Grok 及 Cursor 等主流 CLI,並透過統一的 `omc ask` 指令進行路由,自動處理正確的旗標選擇、構件持久化及供應商版本相容性。開發者只需提供目標平台與問題或任務,Ask 技能便會自動呼叫對應的 CLI 並將結果寫入 `.omc/artifacts/ask/` 目錄下的 Markdown 檔案,方便後續檢索與整合。此技能特別適用於需要跨平台比較回覆、協同工作或逐步實施計劃的場景,能顯著提升開發效率與工作流程的結構化程度。

相容平台✓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 {{ARGUMENTS}}

請勿手動建構原始的供應商 CLI 指令。 絕對不要直接執行 codex、claude、gemini、agy、grok 或 cursor-agent 來完成此技能。omc ask 包裝器會自動處理正確的旗標選擇、構件持久化及供應商版本相容性。手動組合供應商 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/<供應商>-<簡短名稱>-<時間戳記>.md

任務:{{ARGUMENTS}}

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

相關技能