gemini-peer-review
🖥️ Claude Code Only - Requires terminal access to execute Gemini CLI commands.
npx skills add majiayu000/claude-skill-registry --skill gemini-peer-review --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Leverages Google's Gemini CLI to provide a second AI perspective for peer review, architecture validation, design cross-validation, security analysis, and holistic codebase assessment. It is intended for high-stakes decisions, complex architectures, and large codebases, and must be explicitly invoked using the skill syntax.
How it works
- The skill is invoked explicitly by Claude using:
skill: "gemini-peer-review"
- When invoked, Claude prepares a context for Gemini, including relevant code, architecture diagrams, and specific questions or concerns.
- It uses Gemini CLI commands (via non-interactive prompts or multi-line prompts) to perform analysis, potentially including multimodal inputs (diagrams, designs) and full-context reviews up to large codebases.
- The workflow supports loading preparation guidelines, context structure templates, and common Gemini invocation patterns from referenced guidance, then executing a CLI prompt such as:
cat <<'EOF' | gemini
[prepared context and question here]
EOF
-
Outputs from Gemini are then synthesized with Claude's analysis using a synthesis framework to produce an integrated recommendation, noting agreements, disagreements, complementary insights, and actionable next steps.
-
The skill emphasizes explicit invocation, handling of potential Gemini unavailability or API limits, and structured synthesis outputs.
When to use it
- Use when making high-stakes architecture decisions, evaluating multiple design alternatives, reviewing security-critical code, validating complex refactors, or analyzing very large codebases requiring extensive context.
- Do not use for simple, straightforward implementations, when a single opinion suffices, or when Gemini CLI is unavailable.
- The skill explicitly instructs Claude to invoke Gemini only through the defined skill syntax and prompts.
What it can touch
- Gemini CLI interaction through terminal-based commands as per the provided invocation patterns.
- Contextual input including code modules, architecture descriptions, and multimodal assets if available, formatted per Gemini guidance.
Caveats
- Requires explicit invocation and terminal access to Gemini CLI.
- Output depends on Gemini availability and API limits; potential fallbacks to Claude-only analysis may occur if unavailable.
- The approach relies on cross-AI synthesis; users should consider both perspectives and apply integrated recommendations.
--- name: gemini-peer-review description: [CLAUDE CODE ONLY] Leverage Gemini CLI for AI peer review, second opinions on architecture and design decisions, cross-validation of implementations, security analysis, alternative approaches, and holistic codebase analysis. Requires terminal access to execute Gemini CLI commands. Use when making high-stakes decisions, reviewing complex architecture, analyzing large codebases (1M token context window), or when explicitly requested for a second AI perspective. Must be explicitly invoked using skill syntax. license: Complete terms in LICENSE.txt environment: claude-code --- # Gemini Peer Review - AI Collaboration Skill 🖥️ **Claude Code Only** - Requires terminal access to execute Gemini CLI commands. Enable Claude Code to leverage Google's Gemini CLI for collaborative AI reasoning, peer review, and multi-perspective analysis of code architecture, design decisions, and implementations. ## Core Philosophy **Two AI perspectives are better than one for high-stakes decisions.** This skill enables strategic collaboration between Claude Code (Anthropic) and Gemini (Google) for: - Architecture validation and critique - Design decision cross-validati
- Core Philosophy
- When to Use Gemini Peer Review
- High-Value Scenarios
- How to Invoke This Skill
- Codex vs Gemini: Which Peer Review Skill?
- Core Workflow
- 1. Recognize Need for Peer Review
- 2. Prepare Context for Gemini
- 3. Invoke Gemini CLI
- 4. Synthesize Perspectives
- 5. Present Balanced Analysis
- Use Case Patterns
- 1. Architecture Review
- 2. Design Decision Validation
cat <<'EOF' | gemini gemini "Analyze this architecture diagram: [question]" @architecture.png Install via npm (recommended) npm install -g @google/gemini-cli Verify installation gemini --version Option 1: OAuth login (recommended) gemini login Option 2: API key gemini config set apiKey YOUR_API_KEY
What does the gemini-peer-review skill do?
🖥️ Claude Code Only - Requires terminal access to execute Gemini CLI commands.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill gemini-peer-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
