菜单
Ask the user for maximum clarifications before acting on a prompt. Use when the user wants to ensure all ambiguity is resolved before work begins.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
After a code change, test it end-to-end (bash, browser, or computer use — whichever fits) and then run `/simplify` to review and clean up the changed code. Use to confirm a change works and is tidy before wrapping up.
Create a git commit and push it
Create a git commit
Write or refresh a README that earns the reader's attention — short, honest, with a real visual. Tailored to the project type.
Greenfield product spec for an empty repo. Clarifies scope, then challenges the idea — checking whether it already exists and whether the pain is real — before writing a concise spec.md.
Create multiple git commits, one per concern, from changes in the working tree, then push them
| name | clarify |
| description | Ask the user for maximum clarifications before acting on a prompt. Use when the user wants to ensure all ambiguity is resolved before work begins. |
| argument-hint | ["prompt or task description"] |
| disable-model-invocation | true |
$ARGUMENTS
Resolve all ambiguity before acting. Do NOT implement during clarification — only after answers are in.
AskUserQuestion.AskUserQuestion call. Only loop if the answers genuinely open new ambiguity — not to chase every minor detail./clarify for a reason. Ask one confirmation question ("I read this as X — proceed?") before implementing.