Send questions, review requests, or implementation tasks to a supported local AI command-line tool through one shared command. The wrapper handles provider-specific options and saves the result as a Markdown file for later reference.
Process-first advisor routing for Claude, Codex, Gemini, Antigravity, Grok, Cursor, or Muse via `omc ask`, with artifact capture and no raw CLI assembly
Review the instructions the agent will receive before you install.
Use OMC's canonical advisor skill to route a prompt through the local Claude, Codex, Gemini, Antigravity, Grok, Cursor, or Muse CLI and persist the result as an ask artifact.
/oh-my-claudecode:ask <claude|codex|gemini|antigravity|grok|cursor|muse> <question or task>
Examples:
/oh-my-claudecode:ask codex "review this patch from a security perspective"
/oh-my-claudecode:ask gemini "suggest UX improvements for this flow"
/oh-my-claudecode:ask antigravity "suggest UX improvements for this flow"
/oh-my-claudecode:ask claude "draft an implementation plan for issue #123"
/oh-my-claudecode:ask cursor "apply this implementation plan"
/oh-my-claudecode:ask muse --agent-prompt critic "review this plan"
Required execution path — always use this command:
omc ask {{ARGUMENTS}}
Do NOT manually construct raw provider CLI commands. Never run codex, claude, gemini, agy, grok, cursor-agent, or muse directly to fulfill this skill. The omc ask wrapper handles correct flag selection, artifact persistence, and provider-version compatibility automatically. Manually assembling provider CLI flags will produce incorrect or outdated invocations.
claude --version
codex --version
gemini --version
agy --version
grok --version
cursor-agent --version
muse --version
agy
binary per the official Antigravity instructions (inspect
any installer before running it). Verify: agy --version
Platform note:
omc ask antigravityis supported on macOS/Linux. On Windows it is guarded with a clear error, becauseagy --printtakes the prompt as an argv value (it cannot read stdin) and has known upstream Windows-plimitations; useomc ask geminion Windows.
--prompt-file. The wrapper uses private temporary files for prompts, including role files with YAML frontmatter. Muse runs with approvals disabled and preserves its configured sandbox behavior.omc ask writes artifacts to:
.omc/artifacts/ask/<provider>-<slug>-<timestamp>.md
Task: {{ARGUMENTS}}
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Write or revise instructions, specifications, tickets, and skill files so an agent can act without prior chat history. Make rules checkable, explain their reasons, define completion criteria, and keep authoritative information in one place.
Simplify bloated AI-generated code by removing dead code, duplicated logic, and unnecessary layers while checking that existing behavior stays intact. Use a limited cleanup scope, verify changes with relevant checks, or request a review without edits.
Review module relationships and change history to identify structural improvements in a codebase. Receive ranked candidates with file references, suggested changes, and risks, plus a recommendation for where to start, without modifying code.
Turn an unclear idea into linked decision tickets on a repository’s issue tracker. Work through one decision per session, record outcomes and dependencies, and prepare a brief defining the objective, scope, and exclusions for delivery.
Turn a short product idea into working code through requirements analysis, technical planning, implementation, testing, and review. It coordinates agents across these stages, fixes detected problems, and reports assumptions that still need a human decision.
Run repeated change-and-evaluation cycles for one predefined improvement mission within an explicit runtime limit. Save each evaluation as JSON and each decision in readable Markdown logs, with support for periodic reruns through Claude Code native cron.