メニュー
Rubber duck tutor — auto-detects which review mode to run. Use when the user says "duck", "tutor", "quiz me", "do I understand this", or mentions rubber-stamping or learning while coding. For a specific phase use /duck-prebuild, /duck-verify, /duck-review, or /duck-orient.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Set up worktree-plus for a repo — manage git config (baseBranch, branchPrefix, dirBase, guessRemote) and build the .worktreeinclude / .worktreelink files by scanning which gitignored files actually exist. Use when the user asks to set up or configure worktree-plus, view or change worktree settings, reset the plugin config, or decide which gitignored files should be copied or symlinked into new worktrees.
Delegate an implementation task to Codex, then Claude reviews the result. Use when asked "codex rescue", "delegate to codex", "have codex do it", or wants Codex to implement or fix something.
Check Codex CLI, auth, Official plugin status, and configure defaults. Use when asked "codex setup", "configure codex", "install codex", or when another codex-advisor skill reports setup issues.
Diagnose Claude Code environment health — context budget, description obesity, trigger collisions, hooks, MCP, plugins, CLAUDE.md, memory, and skill-security scan. Use when asked to audit the environment, check context budget, review plugins, or scan installed skills for risky patterns.
Visualize git diffs as interactive HTML reports with architecture diagrams, change analysis, and side-by-side split-diff of the actual changed code. Use when asked to visualize, review, or summarize a diff, branch, commit, or PR — including seeing the real changed lines, not just a summary. Accepts branch names, commit hashes, HEAD, PR numbers, or commit ranges.
Convert any markdown document into a diagram-enriched visual HTML report. Use when asked to visualize, illustrate, or create a visual report from a document with diagrams. Single md file input. Also trigger when: "make this document visual", "add diagrams to this doc", "turn this markdown into a report", "visualize this README/ADR/spec", or any request to render a document with embedded diagrams.
| name | duck |
| description | Rubber duck tutor — auto-detects which review mode to run. Use when the user says "duck", "tutor", "quiz me", "do I understand this", or mentions rubber-stamping or learning while coding. For a specific phase use /duck-prebuild, /duck-verify, /duck-review, or /duck-orient. |
| disable-model-invocation | true |
| allowed-tools | Read Grep Glob Bash(git diff *) Bash(git log *) Bash(git status *) Bash(bash ${CLAUDE_PLUGIN_ROOT}/skills/ducking/scripts/log-gap.sh *) Bash(bash ${CLAUDE_PLUGIN_ROOT}/skills/ducking/scripts/read-config.sh *) |
Auto-detects which mode fits the user's current state and routes to the matching mode skill. Read ../ducking/engine.md for shared persona, principles, and session-management rules — they apply to every mode.
| Trigger phrase / state | Mode skill |
|---|---|
| "build this for me" / stated implementation intent, no plan or code yet | /duck-prebuild |
Active plan in conversation (or .claude/orientation.md-adjacent design doc) | /duck-prebuild |
| Files recently created/modified in this session | /duck-verify |
Uncommitted changes (git diff --stat non-empty) | /duck-review |
| User new to the repo, returning after long break, "where should I even start" | /duck-orient |
| None of the above | Ask the user which phase they want |
Check in this order — first match wins:
/duck-prebuild/duck-prebuildgit diff --stat shows a real diff → /duck-review/duck-verify/duck-orientIf the user named a mode (prebuild, verify, review, orient — or the older design/plan words, both alias to prebuild), suggest the matching /duck-<mode> command and stop — don't run the mode flow inline. The dedicated mode skill carries the full instructions for that flow.
If the user passed $ARGUMENTS and it matches a known mode word, hand off to /duck-<mode> (map design/plan → prebuild; otherwise use $ARGUMENTS as-is):
"🦆 Quack — you want
/duck-<mode>. Call it directly instead."
Otherwise apply the detection order above.
If the user wants to keep going inside /duck instead of switching to the mode-specific command, run the matching mode's flow inline. The mode-specific SKILL.md files contain the canonical flows — read the file and follow it.
All persona, opening line, "Wait for their answer", Confidence Check, Intensity Scaling, Uncertainty Check, Session Wrap-up + gap persistence, Branch-first workflow + fallback, Session Limits, Facilitation, and Gotchas live in ../ducking/engine.md. Read it before running any flow.