rubber-duck-reviewlisted

# Rubber Duck Review Get a second opinion on code changes from a different model while you keep ownership of the task. ## When to Apply Use this skill when someone asks for: - `/rubber-duck-review` - "rubber duck my changes" - "get a second opinion on this" - "review this with another model" ## Workflow ### 1. Pick the reviewer - Prefer a dedicated review tool when one is available. - Use a reviewer that is different from the current model when possible. - If no dedicated tool exists, fall back to a read-only CLI invocation through this skill's `scripts/run-review.mts` (step 3). Pick the reviewer by which model *you* are: - If you are currently using **Claude** → `codex`, fallback `copilot`. - If you are currently using **Codex or GitHub Copilot** → `claude`, fallback `copilot`. - **Never** let the reviewer write files, edit code, or run unrestricted shell commands. - The script enforces read-only flags: `--sandbox read-only` (codex) / `--permission-mode plan` (claude) / a read-only tool allow-list (copilot). - Read-only still lets the reviewer self-check: it can run read-only commands (grep, `git diff`, typecheck; copilot can only read and grep files) but writes are blocked. That self-checking makes findings concrete. - Note: a read-only sandbox can block temp-dir creation, so the reviewer may skip tests that need to write. ### 2. Craft the prompt - Ask for a review of the relevant changes and surrounding context only. - Always include: `This is a review-o