菜单
Ask Gemini via local CLI and capture a reusable artifact
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Diagnose and fix oh-my-qwencode installation issues
Guide on using oh-my-qwencode plugin
Run deep investigation of architecture, bugs, performance issues, or dependencies and return structured findings with file:line evidence. Use when a user says 'analyze', 'investigate', 'why does', 'what's causing', or needs root cause analysis before making changes. Routes to architect agent or Qwen Code MCP for thorough cross-file reasoning.
Ask Claude via local CLI and capture a reusable artifact
Full autonomous execution from idea to working code
Fix build and TypeScript errors with minimal changes
| name | ask-gemini |
| description | Ask Gemini via local CLI and capture a reusable artifact |
Use the locally installed Gemini CLI as a direct external advisor for brainstorming, design feedback, and second opinions.
/ask-gemini <question or task>
Run Gemini through the canonical OMQ CLI command path (no MCP routing):
omq ask gemini "{{ARGUMENTS}}"
Exact non-interactive Gemini CLI command from gemini --help:
gemini -p "{{ARGUMENTS}}"
# equivalent: gemini --prompt "{{ARGUMENTS}}"
If needed, adapt to the user's installed Gemini CLI variant while keeping local execution as the default path.
Legacy compatibility entrypoints (./scripts/ask-gemini.sh, npm run ask:gemini -- ...) are transitional wrappers.
If gemini is not found, do not switch to MCP.
Instead:
gemini --version
After local execution, save a markdown artifact to:
.omq/artifacts/gemini-<slug>-<timestamp>.md
Minimum artifact sections:
Task: {{ARGUMENTS}}