agentsclimarketplace
Sign in

Gemini code review

Skill NaluForge/geminicli-cc-plugin/skills/gemini-code-review

This skill should be used when the user asks to review code changes, review a PR, get a second opinion on a diff, cross-check modifications, or perform a security review using Gemini. Relevant when the user says "review this PR with Gemini," "check my diff for bugs," or "get a second opinion on these changes."From its SKILL.md

Install
npx -y skills add NaluForge/geminicli-cc-plugin --skill gemini-code-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.7 KB, as published. Nobody here has run it

Code Review Cross-Check with Gemini

Invoke using /gemini-review or mcp__gemini__gemini_execute with a review-focused prompt.

When to Use Gemini for Review

Gemini provides value as an independent reviewer when:

  • Changes are large (>500 lines) and benefit from fresh eyes
  • Changes touch security-sensitive code (auth, crypto, input validation)
  • You want to catch bugs that familiarity with the code might mask
  • A PR needs review and no human reviewer is immediately available
  • You want a second opinion on architectural decisions in the diff

Gathering Context

Good reviews need full context, not just diffs:

  1. Get the diff: git diff for working changes, gh pr diff N for PRs
  2. Get full file content: Changed lines make more sense with surrounding code. Read the complete files, not just the diff hunks.
  3. Get commit history: git log main..HEAD --oneline shows the intent behind the changes
  4. Get PR description: gh pr view N --json title,body for context on what the PR aims to accomplish

Structuring the Review Prompt

Send Gemini a structured review request:

  • The full diff
  • Complete content of changed files
  • PR description or commit messages for intent
  • Specific areas of concern (if any)

Ask Gemini to check for:

  • Bugs: Logic errors, off-by-one, null/undefined handling
  • Security: Injection, auth bypasses, data exposure, secrets in code
  • Edge cases: Empty inputs, concurrent access, error paths
  • Performance: N+1 queries, unnecessary allocations, missing indexes
  • Consistency: Naming conventions, patterns used elsewhere in the codebase

Parameters

  • model: Prefer pro for large or security-sensitive reviews; flash is sufficient for small diffs
  • timeout_ms: 2400000 (40 minutes) — large diffs and full-repo reviews need extended time
  • include_directories: Directories containing the changed files

Interpreting Results

Group findings by severity:

  • Critical: Must fix before merging (bugs, security, data loss)
  • Warning: Should investigate (logic concerns, missing error handling)
  • Suggestion: Nice to have (style, naming, documentation)

A clean review (no findings) is valuable signal — it means an independent model found nothing concerning. Report this explicitly rather than staying silent.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.