Gemini Peer Review

Gemini Peer Review

Consult Gemini as a coding peer for a second opinion on code quality, architecture decisions, debugging, or security reviews.

Setup

API Key: Set GEMINI_API_KEY as an environment variable. Get a key from https://aistudio.google.com/apikey if you don't have one.

export GEMINI_API_KEY="your-key-here"

Workflow

1. Determine mode from user request (review, architect, debug, security, quick)
2. Read target files into context
3. Build prompt using the AI-to-AI template from references/prompt-templates.md
4. Write prompt to file at .claude/artifacts/gemini-prompt.txt (avoids shell escaping issues)
5. Call the API via the review script:

mkdir -p .claude/artifacts
# Write prompt to file first (step 4), then:
GEMINI_API_KEY="$KEY" python3 plugins/dev-tools/skills/gemini-peer-review/scripts/gemini-review.py \
  --model gemini-2.5-flash \
  --prompt-file .claude/artifacts/gemini-prompt.txt

6. Synthesize — present Gemini's findings, add your own perspective (agree/disagree), let the user decide what to implement

Modes

Code Review

Review specific files for bugs, logic errors, security vulnerabilities, performance issues, and best practice violations.

Read the target files, build a prompt using the Code Review template, call with gemini-2.5-flash.

Architecture Advice

Get feedback on design decisions with trade-off analysis. Include project context (CLAUDE.md, relevant source files).

Read project context, build a prompt using the Architecture template, call with gemini-2.5-pro.

Debugging Help

Analyse errors when stuck after 2+ failed fix attempts. Gemini sees the code fresh without your debugging context bias.

Read the problematic files, build a prompt using the Debug template (include error message and previous attempts), call with gemini-2.5-flash.

Security Scan

Scan code for security vulnerabilities (injection, auth bypass, data exposure).

Read the target directory's source files, build a prompt using the Security template, call with gemini-2.5-pro.

Quick Question

Fast question without file context. Build prompt inline and call with gemini-2.5-flash.

GEMINI_API_KEY="$KEY" python3 plugins/dev-tools/skills/gemini-peer-review/scripts/gemini-review.py \
  --model gemini-2.5-flash \
  --prompt "[Claude Code consulting Gemini] Quick question: What's the best way to handle WebSockets in Workers?"

Model Selection

Override by changing the --model argument. Check current model IDs if errors occur — they change frequently:

curl -s "https://generativelanguage.googleapis.com/v1beta/models?key=$GEMINI_API_KEY" | python3 -c "import sys,json; [print(m['name']) for m in json.load(sys.stdin)['models'] if 'gemini' in m['name']]"

When to Use

Good use cases:

• Before committing major changes (final review)
• When stuck debugging after multiple attempts
• Architecture decisions with multiple valid options
• Security-sensitive code review

Avoid using for:

• Simple syntax checks (Claude handles these faster)
• Every single edit (too slow, unnecessary)
• Questions with obvious answers

Prompt Construction

Critical: Always use the AI-to-AI prompting format. Write the full prompt to a file — never pass code inline via bash arguments (shell escaping will break it).

When building the prompt:

1. Start with the AI-to-AI header from references/prompt-templates.md
2. Append the mode-specific template
3. Append the file contents with clear --- filename --- separators
4. Write to .claude/artifacts/gemini-prompt.txt
5. Call the script with --prompt-file

Reference Files