review-with-gemini

review-with-gemini is a skill for Claude Code from LaStrada/claude. It costs 143 tokens per session (1,270 once invoked), scanned A, original, MIT.

A workflow for sending a code diff to Google’s Gemini command-line tool for an independent review. It returns Gemini’s findings for the developer to assess.

In plain words
What is it for?
Use it to review a Git branch or selected files with Gemini, then classify each reported issue as genuine, irrelevant, or needing further verification.
Why use it?
It provides a second opinion on the changes, which can reveal issues the original author or reviewer missed. The workflow requires confirmation before uploading the diff and avoids specified sensitive files.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Codex; mentions Gemini CLI.

Part of the review-with plugin — 4 skills, 6 commands shipped together

Good fit Use it to review a Git branch or selected files with Gemini, then classify each reported issue as genuine, irrelevant, or needing further verification.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/lastrada/claude/review-with-gemini
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add LaStrada/claude --skill review-with-gemini
Clone the repo
git clone --depth 1 https://github.com/LaStrada/claude

Made for: Claude Code.

Or install review-with, the plugin that ships this one along with the rest of its 4 skills, 6 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for review-with-gemini

README.md
[![agentmods](https://agentmods.dev/badge/skills/lastrada/claude/review-with-gemini/github.svg)](https://agentmods.dev/skills/lastrada/claude/review-with-gemini)
Your own site
<a href="https://agentmods.dev/skills/lastrada/claude/review-with-gemini"><img src="https://agentmods.dev/badge/skills/lastrada/claude/review-with-gemini/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for review-with-gemini

Your own site · 80×15
<a href="https://agentmods.dev/skills/lastrada/claude/review-with-gemini"><img src="https://agentmods.dev/badge/skills/lastrada/claude/review-with-gemini.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 143 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,270 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00143 $0.01270
Opus 5 $0.00072 $0.00635
Sonnet 5 $0.00029 $0.00254
Haiku 4.5 $0.00014 $0.00127

Measured 10d ago against content hash e4353759d531, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

review-with-gemini scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/review-with/skills/review-with-gemini/SKILL.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

review-with-gemini

Send a diff to Google's Gemini CLI for a second-opinion review, then relay findings.

Non-negotiable rules

  1. Confirm upload first. The diff is sent to Google's Gemini API. On the first call in a session, tell the user what will be sent (branch, file count, +X/-Y) and wait for confirmation.
  2. Refuse on sensitive paths. If the diff contains secrets.properties, .env, *.p12, *.keystore, GoogleService-Info.plist, google-services.json, or anything matching *secret*/*credential*/*token* — refuse and warn. Don't upload them even if the user says it's fine.
  3. Always pass -m gemini-2.5-flash. The CLI's bare default has been gemini-3-flash-preview which regularly returns MODEL_CAPACITY_EXHAUSTED, and gemini-2.5-pro hits user-level rate limits if used as a fallback. Pro only on explicit user request. Full rationale in references/troubleshooting.md.
  4. No Kotlin lint auto-format in a review flow. User-specific preference; see feedback_skip_kotlin_lint.md.
  5. Relay, don't agree. Present as "Gemini says:" with a one-line triage (genuine / off / needs-verify) after. The user decides.
  6. Non-interactive only. Always pass -p/--prompt. Never start an interactive gemini session — it blocks the Bash tool.
  7. When the target is a PR, always include existing comments. Before sending the diff, fetch every PR comment via gh — issue comments, review summaries (including CHANGES_REQUESTED), and inline review comments — and (a) inline them as context in the prompt so Gemini doesn't repeat them, and (b) relay them back to the user verbatim using the standard finding format. See "PR-comment fetch" below.

Default invocation

BRANCH=$(git rev-parse --abbrev-ref HEAD)
BASE=$(git remote show origin 2>/dev/null | awk '/HEAD branch/ {print $NF}')  # usually main; dev for some repos
RANGE="$BASE..HEAD"
git diff --stat $RANGE

Tell the user: N files changed, +X/-Y lines. Branch <branch> vs <base>. OK to send to Gemini?

Read the full file on GitHub · 84 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 84 lines · 143 tokens per session scan A e4353759d531

Subscribe to this mod's changes

review-with-gemini is a skill published in the GitHub repository LaStrada/claude (2 stars, last pushed 2mo ago), licensed MIT. It adds 143 tokens to every session and 1,270 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.