agentleFS
Sign inStart free
cukascukas/claudes-ai-buddies/skills/gemini-review/SKILL.md

gemini-review

Skill9 starsChanged 8 months agoMITView on GitHub

Code review via Google Gemini — review uncommitted changes, branches, or commits

7 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use android-kotlin and python.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • alinaqiSkill

    android-kotlin

    Android Kotlin development with Coroutines, Jetpack Compose, Hilt, and MockK testing

    Also in 3 projects that use this

  • rogue-dev-studioSkill

    python

    Python 3.13 with uv package manager via mise. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized `python` work when listed in TEAM.yaml or explicitly requested.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the wrapper script via Bash:

    line 12
  2. Very specific:

    No arguments → review uncommitted changes (--review-target uncommitted)

    line 27
  3. Distinctive:

    Determine working directory: Must be inside a git repository.

    line 30
  4. Distinctive:

    Add your own perspective: if you see issues Gemini missed, or agree with specific points.

    line 35
  5. Distinctive:

    Always verify we're in a git repo: before running. If not, tell the user.

    line 54

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/gemini-review — Code Review via Gemini

Get a code review from Google's Gemini CLI. Reviews uncommitted changes by default, or specify a branch or commit.

How to invoke

Run the wrapper script via Bash:

bash "${CLAUDE_PLUGIN_ROOT}/scripts/gemini-run.sh" \
  --prompt "Additional review instructions (optional)" \
  --cwd "/path/to/repo" \
  --mode review \
  --review-target "uncommitted"

Then read the output file and present the review to the user.

Step-by-step workflow

  1. Determine what to review:
    • No arguments → review uncommitted changes (--review-target uncommitted)
    • User specifies a branch → --review-target branch:branch-name
    • User specifies a commit → --review-target commit:SHA
  2. Determine working directory. Must be inside a git repository.
  3. Build the prompt. The wrapper automatically fetches the diff and builds a review prompt. If the user provides extra instructions (e.g., "focus on security"), pass them as --prompt.
  4. Run gemini-run.sh with --mode review via the Bash tool.
  5. Read the output file using the Read tool.
  6. Present the review to the user. Frame it as "Gemini's code review:" with clear sections.
  7. Add your own perspective if you see issues Gemini missed, or agree with specific points.

Review targets

TargetFlagExample
Uncommitted changes--review-target uncommitted/gemini-review
Branch diff--review-target branch:NAME/gemini-review branch:feature/auth
Specific commit--review-target commit:SHA/gemini-review commit:abc1234

Example invocations

  • /gemini-review — review all uncommitted changes
  • /gemini-review branch:main — review diff from main to HEAD
  • /gemini-review commit:a1b2c3d — review a specific commit
  • /gemini-review "focus on security and SQL injection" — review with extra instructions

Rules

  • Always verify we're in a git repo before running. If not, tell the user.
  • If no changes exist, tell the user there's nothing to review instead of sending an empty diff.
  • Present both perspectives — show Gemini's review, then add your own observations.
  • Don't auto-apply suggestions — present findings and let the user decide what to fix.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free