Gemini Review

Get a second-opinion review of the current diff (or a chosen focus — architecture, security, docs, design, performance, tests) from the Gemini CLI, then present its findings alongside your own analysis. Single-reviewer counterpart to /codex-review and /review-panel; needs the `gemini` CLI installed. Triggers on `/gemini-review [focus]`, "gemini review this", "get a gemini second opinion on this diff".

37 stars 7 forksAI, LLMs & Agents

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add iamneilroberts/claude-skills --skill gemini-review
Manual install
git clone --depth 1 https://github.com/iamneilroberts/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/gemini-review ~/.claude/skills/gemini-review

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Gemini External Review

Invoke the Gemini CLI (Google's CLI agent) as an external reviewer for a second opinion.

**Arguments:** `$ARGUMENTS`

## Determine Review Type

Parse `$ARGUMENTS` to determine the review focus. If empty, default to `code`.

| Argument | Focus |
|----------|-------|
| *(empty)* | Code review — bugs, security, quality, performance |
| `code` | Code review — bugs, security, quality, performance |
| `architecture` or `arch` | Architecture — structure, patterns, separation of concerns, scalability |
| `security` or `sec` | Security audit — vulnerabilities, auth issues, data exposure, OWASP |
| `docs` | Documentation — accuracy, completeness, clarity, examples |
| `design` | Design review — API design, naming, abstractions, DX |
| `performance` or `perf` | Performance — bottlenecks, memory, queries, caching |
| `test` or `tests` | Test review — coverage, edge cases, test quality, flaky tests |
| Anything else | Use the argument text as a custom review prompt/focus |

## Your Task

1. **Gather context:**
   - Read the project's README or main docs if present.
   - Run `git status`, `git diff --stat`, `git diff` (staged + unstaged; keep it reasonable size),
     and `git log --oneline -10`.
   - Identify the stack (package.json, Cargo.toml, pyproject.toml, etc.) and note project structure.

2. **Prepare the review request** — build a prompt for Gemini with: project name/description,
Read the full skill on GitHub

Details

Skill name
gemini-review
Path
skills/gemini-review/SKILL.md
Repo updated
21 August 2026

FAQ

What does the Gemini Review skill do?

Get a second-opinion review of the current diff (or a chosen focus — architecture, security, docs, design, performance, tests) from the Gemini CLI, then present its findings alongside your own analysis. Single-reviewer counterpart to /codex-review and /review-panel; needs the `gemini` CLI installed. Triggers on `/gemini-review [focus]`, "gemini review this", "get a gemini second opinion on this diff".

How do I install the Gemini Review skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add iamneilroberts/claude-skills --skill gemini-review. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Gemini Review popular?

It lives in iamneilroberts/claude-skills, which has 37 GitHub stars and 7 forks.

Related skills

Brag

37

iamneilroberts/claude-skills

Memorialize something you just built by generating a self-contained "showcase" page for it — a persuasive, good-looking deep dive: what it is, why it's impressive, how it works — with a screenshot if one can be found or captured, and links to related showcase pages. This is the sales/hype-leaning counterpart to /write-post (which drafts a neutral, no-BS technical post); reach for /brag when you want it to sell. Fast by design, like /idea: ask only what's needed, build the page, don't turn it into a project. Triggers on `/brag <subject>`, "brag about this", "make a showcase page for X", "write

Writing & Content

Branch

37

iamneilroberts/claude-skills

Create an isolated git worktree for a task and log it to a shared work journal, so multiple Claude Code sessions run in parallel without racing on HEAD, uncommitted edits, or the index. Subcommands: `list`, `done <slug>`, `update` (heartbeat), `coord <message>` / `coord clear <slug>` (cross-session constraints). Triggers on `/branch`, "start in a worktree", "isolate this work", "parallel session", "heartbeat the journal".

Git & Code Review

Claude Code Best Practices

37

iamneilroberts/claude-skills

Use when asked about Claude Code workflow, prompt caching cost, session economics, CLAUDE.md hygiene, context-window management, plan mode, permission modes, hooks, skills, subagents, checkpointing/rewind, parallel sessions, worktrees, headless/CI usage, the Agent SDK, slash commands, MCP configuration, or "what's the right way to use Claude Code for X". Also use proactively BEFORE suggesting /model, /compact, fast-mode toggle, or editing CLAUDE.md mid-session, since those bust the system cache.

AI, LLMs & Agents

LLM Tools

37

iamneilroberts/claude-skills

Use when a session is about to bulk-read 3+ files or any single file over ~400 lines, generate predictable boilerplate (tests, fixtures, config scaffolds, doc templates), or compress a long session transcript — and a cheap OpenAI-compatible worker model (Kimi, DeepSeek, OpenRouter, local Ollama) is available via the llm-ask/llm-write/llm-extract CLIs.

AI, LLMs & Agents

Frontier Spend

37

iamneilroberts/claude-skills

Use when planning how to spend scarce or expiring access to a premium frontier-tier model (usage-capped, deprecation cliff, "how should I spend my remaining premium-model budget", 2x burn rate, model leaving the plan) — before starting any premium-model session or writing a spend plan.

AI, LLMs & Agents

Review

37

iamneilroberts/claude-skills

The top-level review verb — decide WHETHER, WHEN, WHICH, and HOW HARD to review a change before reaching for a review tool. Assesses the situation (a plan vs a diff, the risk surface, what changed since the last review, rounds already spent), picks the lightest review shape the risk justifies (in-session self-review → cross-model → multi-model panel), sets an initial round budget it will extend only on convergence, and dispatches. Exists to stop review spirals: reviewing before the plan is formed, reviewing after every trivial edit, or looping a reviewer past the point of convergence. Triggers

AI, LLMs & Agents

Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.