gemini-review

Automate code reviews by querying Gemini on Git branch diffs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/fwojciec/quiver --skill gemini-review-fwojciec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gemini-review
Source: https://github.com/fwojciec/quiver/tree/main/.claude/skills/gemini-review
Command: npx skills add https://github.com/fwojciec/quiver --skill gemini-review-fwojciec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, gemini.

What problem does it solve?

This Skill enables teams to obtain an independent, automated code review from Gemini for changes staged or committed on a feature branch, improving review coverage and speed.

Core Features & Use Cases

  • Automated Code Review: Request a Gemini review for diffs between the current branch and a base branch.
  • PR Context & Standards: Include PR description context when available and align with project standards using CLAUDE-like rules.
  • Use Case: When preparing a pull request, run this skill to get a structured critique of the changes before submitting.

Quick Start

BASE_BRANCH="${ARGUMENTS:-main}" Determine what to review: if there are staged changes, Gemini reviews them; otherwise, review commits on the branch relative to BASE_BRANCH. Run gemini to generate a structured review.

Frequently Asked Questions about gemini-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get an automated code review for my Git branch changes?

To get an automated code review for your Git branch changes, you can use a tool that queries Gemini on your current branch diffs. It evaluates staged changes or commits relative to a base branch to generate a structured critique.

Can I include pull request context when running a Gemini code review?

Yes, you can include pull request context during a Gemini code review. The process extracts the PR description using the GitHub CLI to align the generated critique with the intended changes and project standards.

Do I need the GitHub CLI to run a Gemini review on my local Git diff?

Yes, you need the GitHub CLI installed to run this Gemini review on your local Git diff. The workflow requires the git CLI, the GitHub CLI, and the Gemini review tool to analyze diffs and pull request context.

What is the best way to review staged changes before submitting a pull request?

The best way to review staged changes before submitting a pull request is to run an automated Gemini review. It detects staged changes automatically and generates a structured critique to improve code quality prior to submission.

How does an automated review handle commits on a feature branch relative to main?

An automated review handles commits on a feature branch by comparing them relative to a specified base branch like main. If no staged changes exist, it evaluates the committed diffs to produce the structured critique.

What are the limitations of using Gemini for code reviews on feature branches?

Limitations of using Gemini for code reviews include its dependency on local CLI tools like git and gh for context. It requires a configured base branch and properly staged or committed changes to generate an accurate critique.