多模型AI辩论工具

Requirements

This toolkit runs on macOS, Linux, or WSL (Windows Subsystem for Linux). Windows users: install WSL first. Native Windows PowerShell also works for setup and all non-debate commands; only /ask-gpt and /ask-gemini require bash/WSL.

---

`/explore` - Understand before you build

Asks 3-4 focused questions about scope, success criteria, and constraints before any code is written. Has two modes: scoping (you have a concrete idea, pressure-test the scope) and vision (you're thinking big-picture, challenge the premise itself). It picks a mode by reading your input, then asks you to confirm. You can switch modes any time. Useful when you're not yet sure what you're actually building.

Full prompt: .claude/commands/explore.md

`/execute` - Build it, update the plan as you go

Walks through the plan step by step, updating status emojis and progress in real time. Spawns parallel agents for [parallel] steps, runs [sequential] steps in order. Stops on critical blockers (e.g. the plan assumed an API supports a feature it doesn't) instead of pushing through a broken plan.

Full prompt: .claude/commands/execute.md

Manual Setup (run the script yourself)

Prefer to run the setup script yourself? Pick the script that matches your shell:

Bash (WSL, macOS, Linux):

bash /path/to/llm-peer-review/scripts/setup/setup.sh /path/to/your-project

PowerShell (setup and non-debate commands - see Requirements):

powershell -ExecutionPolicy Bypass -File C:\path\to\llm-peer-review\scripts\setup\setup.ps1 -Target "C:\path\to\your-project"

Or run from inside your project directory (no target needed):

cd /path/to/your-project
bash /path/to/llm-peer-review/scripts/setup/setup.sh

Note: If you run the script from inside the toolkit repository without specifying a target, it shows an error to prevent accidentally copying files into the wrong place.

Preview first (optional): add --dry-run (bash) or -DryRun (PowerShell) to see exactly what an install or upgrade would do - version gap, migrations, files that would be overwritten, custom files that are left alone, and where backups go - without changing anything:

bash /path/to/llm-peer-review/scripts/setup/setup.sh /path/to/your-project --dry-run

Every real run prints the same pre-flight report before it touches anything.

What setup does: - Copies into your project: commands, skills (including the prebuilt HTML shells), both rules files (toolkit.md, html-outputs.md), and all runtime and helper scripts (ask-gpt.js, ask-gemini.js, browse.js, generate-index.js, render-html.js, session-init.js, open-artifact.sh), plus VERSION and .env.local.example. Detects and removes any legacy INDEX.md. CODEBASE_MAP.md (a semantic map of your project) is generated on your first /explore run, when Claude auto-invokes /index. - Preserves your work: CLAUDE.md, LESSONS.md (plus its companion LESSONS-detail.md), and settings.local.json are skipped if they already exist - those are yours to customize. Custom files you add inside .claude/commands/, .claude/skills/, .claude/scripts/, or .claude/rules/ are never modified or deleted (this guarantee is covered by the toolkit's installer test suite), and anything setup does overwrite is backed up to a timestamped .toolkit-backup-* folder first. - Always updates: the managed rules files (.claude/rules/toolkit.md, .claude/rules/html-outputs.md). - Stays in the toolkit repo: setup scripts (setup.sh, setup.ps1, install-alias.*) are never copied.

See How It Works for details on which files are yours vs. managed by the toolkit.

One install covers everything - it stays inside .claude/scripts/ so your

For /review-browser, install the Chromium browser:

npx --prefix .claude/scripts playwright-core install chromium

On Linux/WSL, also: sudo npx playwright-core install-deps chromium

```

The debate commands and the browser command are optional. Skip the API keys if you don't want /ask-gpt and /ask-gemini. Skip the Chromium install if you don't want /review-browser. The core workflow commands work either way.

</details>

Never set up a dev environment before? Follow the step-by-step guide in SETUP.md. It covers Windows (WSL), Mac, Node.js, GitHub CLI, Cursor, and API keys - everything you need from scratch.

Not using Cursor? The setup guide assumes Cursor, but the toolkit works with any editor that supports Claude Code. Copy the relevant setup page into any AI assistant and ask it to rewrite the steps for your editor.

---

Install the toolkit's runtime packages (one-time, stays in .claude/scripts/).

npm install --prefix .claude/scripts

Example

You: /ask-gpt

Claude: What would you like me to review?
        1. Plan    2. Code    3. Branch    4. Feature    5. Other

You: Review the auth middleware

Claude: [Gathers context → sends to ChatGPT → they debate 3 rounds]

        --- Summary ---
        Agreed: Add token expiry check, extract magic numbers

        Recommended Actions:
        - [ ] Add token expiry validation
        - [ ] Move 3600 to TOKEN_EXPIRY_SECONDS

        Want me to implement these?

You: Yes

Want a different perspective? Run /ask-gemini next.

API costs: Each 3-round debate typically costs $0.01-$0.10 in API credits depending on context size. You'll need an OpenAI and/or Gemini API key with credits. See API-KEYS.md for a step-by-step setup guide.

Choosing what to review:

<img src="docs/images/ask-gpt-prompt.png" alt="ask-gpt prompt showing review options" width="700">

---

Open .env.local and paste your API keys

Edit .env.local and paste your OPENAI_API_KEY and GEMINI_API_KEY

For /ask-gpt and /ask-gemini, set up your API keys:

cp .env.local.example .env.local

AI debate commands (/ask-gpt, /ask-gemini): set up API keys

cp .env.local.example .env.local

The Workflow

If the diagram doesn't render: /worktree (optional) -> /explore -> /create-plan -> /execute -> /review -> /ask-gpt or /ask-gemini -> /document

You don't have to use every command every time. Following the order prevents the most common mistake: coding before you've thought it through.

Want to see this in action? Follow the 5-minute walkthrough in DEMO-SCRIPT.md.

Working on multiple things at once? Use /worktree first to create an isolated copy, then open it in a new Cursor window and run /explore there.

---

project's own package.json is never touched.

npm install --prefix .claude/scripts

Browser QA (/review-browser): install Chromium

npx --prefix .claude/scripts playwright-core install chromium

Troubleshooting

• Commands don't show up in Cursor - Make sure .claude/commands/ exists in your project root with .md files inside. The editor workspace root must be the folder that contains .claude/.
• /ask-gpt or /ask-gemini fails - Check that npm install --prefix .claude/scripts was run and .env.local has valid API keys.
• /ask-gpt or /ask-gemini prints a "deprecated model" warning - v4.5.0 auto-overrides outdated GPT_MODEL or GEMINI_MODEL env values with the current default. Edit .env.local to remove or update the stale value if you want to silence the warning. See API-KEYS.md.
• "setup.sh: command not found" - Run the full command from the setup instructions, not just setup.sh on its own.
• "target directory does not exist" - Create the project folder first: mkdir -p /path/to/project
• Script errors with /bin/bash^M or "bad interpreter" - Line-ending issue. Your shell scripts have Windows-style line endings (CRLF) instead of Unix-style (LF). Easiest fix: delete the folder and clone fresh. Advanced fix: run git add --renormalize . && git checkout -- . in the repo.
• I customized a toolkit file and upgraded - where did it go? - The setup script preserves your original at .toolkit-backup-<timestamp>/ at the project root before overwriting. Copy it back if you want to keep your version. Safe to delete the backup directory when done.
• Setup one-liner fails partway through - Safe to rerun the command. Leftover /tmp/tmp.* folders are harmless and can be deleted. .toolkit-backup-*/ directories from prior runs are also safe to delete once you have confirmed you do not need the originals.
• Commands seem outdated or missing sections - Delete any toolkit command files from ~/.claude/commands/. Global copies override project commands and cause stale behavior. The setup script warns about this automatically.

---