Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From oh-my-claudecode
Process-first advisor routing for Claude, Codex, or Gemini via `omc ask`, with artifact capture and no raw CLI assembly
npx claudepluginhub dropsyoon/oh-my-claudecode --plugin oh-my-claudecodeHow this skill is triggered — by the user, by Claude, or both
Slash command
/oh-my-claudecode:askThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use OMC's canonical advisor skill to route a prompt through the local Claude, Codex, or Gemini CLI and persist the result as an ask artifact.
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
Use OMC's canonical advisor skill to route a prompt through the local Claude, Codex, or Gemini CLI and persist the result as an ask artifact.
/oh-my-claudecode:ask <claude|codex|gemini> <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 claude "draft an implementation plan for issue #123"
Required execution path — always use this command:
omc ask {{ARGUMENTS}}
Do NOT manually construct raw provider CLI commands. Never run codex, claude, or gemini 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
omc ask writes artifacts to:
.omc/artifacts/ask/<provider>-<slug>-<timestamp>.md
Task: {{ARGUMENTS}}