skilld
All skills
google-gemini avatar

/code-reviewer

@b703c87
by google-geminigoogle-gemini/gemini-cli107k stars
14,665

Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.

Ask your Agent

Use this Skill: https://skilld.dev/gh/google-gemini/gemini-cli/code-reviewer

This session only. Nothing lands on disk.

SKILL.md

≈56 tokens always: the name and description. ≈732 when used: this file.

Code Reviewer

This skill guides the agent in conducting professional and thorough code reviews for both local development and remote Pull Requests.

Workflow

1. Determine Review Target

  • Remote PR: If the user provides a PR number or URL (e.g., "Review PR #123"), target that remote PR.
  • Local Changes: If no specific PR is mentioned, or if the user asks to "review my changes", target the current local file system states (staged and unstaged changes).

2. Preparation

For Remote PRs:
  1. Checkout: Use the GitHub CLI to checkout the PR.
    gh pr checkout <PR_NUMBER>
  2. Preflight: Execute the project's standard verification suite to catch automated failures early.
    npm run preflight
  3. Context: Read the PR description and any existing comments to understand the goal and history.
For Local Changes:
  1. Identify Changes:
    • Check status: git status
    • Read diffs: git diff (working tree) and/or git diff --staged (staged).
  2. Preflight (Optional): If the changes are substantial, ask the user if they want to run npm run preflight before reviewing.

3. In-Depth Analysis

Analyze the code changes based on the following pillars:

  • Correctness: Does the code achieve its stated purpose without bugs or logical errors?
  • Maintainability: Is the code clean, well-structured, and easy to understand and modify in the future? Consider factors like code clarity, modularity, and adherence to established design patterns.
  • Readability: Is the code well-commented (where necessary) and consistently formatted according to our project's coding style guidelines?
  • Efficiency: Are there any obvious performance bottlenecks or resource inefficiencies introduced by the changes?
  • Security: Are there any potential security vulnerabilities or insecure coding practices?
  • Edge Cases and Error Handling: Does the code appropriately handle edge cases and potential errors?
  • Testability: Is the new or modified code adequately covered by tests (even if preflight checks pass)? Suggest additional test cases that would improve coverage or robustness.

4. Provide Feedback

Structure
  • Summary: A high-level overview of the review.
  • Findings:
    • Critical: Bugs, security issues, or breaking changes.
    • Improvements: Suggestions for better code quality or performance.
    • Nitpicks: Formatting or minor style issues (optional).
  • Conclusion: Clear recommendation (Approved / Request Changes).
Tone
  • Be constructive, professional, and friendly.
  • Explain why a change is requested.
  • For approvals, acknowledge the specific value of the contribution.

5. Cleanup (Remote PRs only)

  • After the review, ask the user if they want to switch back to the default branch (e.g., main or master).

Source: SKILL.md on GitHub

Third-party checks

1 warning16d5 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    This skill facilitates code reviews for local changes and remote Pull Requests. It includes security considerations regarding the execution of project-specific verification scripts and the processing of external code changes, which are standard for code review workflows.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: MEDIUM · 1 issue

  • Runlayer7mo

    1 file scanned · No issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at b703c87. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 days ago.

Activeupdated 8 months ago

Topics

README badge

README badge for google-gemini/gemini-cli/code-reviewer

What it does

Guides the agent through structured code reviews of local changes or remote PRs, analyzing correctness, maintainability, security, and test coverage. Supports both `git diff` inspection and GitHub PR checkout workflows with optional preflight verification.

Generated from the current SKILL.md.

Frequently asked

Does this skill review both local changes and pull requests?
Yes. It handles local staged or working tree changes via git diff, and remote PRs by number or URL using the GitHub CLI to checkout and review.
What does the skill evaluate during a code review?
It analyzes correctness, maintainability, readability, efficiency, security, edge case handling, and test coverage. Feedback is structured as critical issues, improvements, and optional nitpicks.
Does this skill run automated checks before reviewing?
For remote PRs, it can run the project's preflight suite (npm run preflight). For local changes, it optionally suggests running preflight if changes are substantial.
Can this skill work with GitHub repositories?
Yes. It uses the GitHub CLI (gh) to checkout and review remote PRs. Local reviews work with any git repository.

Generated from the current SKILL.md. These answers refresh after source changes.