code-reviewer

Review local changes and remote Pull Requests using Git and GitHub CLI.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/clevergadget/hierophage-cli --skill code-reviewer-clevergadget
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/clevergadget/hierophage-cli/tree/main/.gemini/skills/code-reviewer
Command: npx skills add https://github.com/clevergadget/hierophage-cli --skill code-reviewer-clevergadget

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers perform thorough, consistent code reviews for both local changes (staged or working tree) and remote Pull Requests, reducing review time and improving overall code quality.

Core Features & Use Cases

  • Target Identification: Determines whether to review local changes or a remote PR by ID or URL.
  • Structured Evaluation: Uses a checklist aligned with project standards to assess correctness, maintainability, readability, and security.
  • Context-Aware Review: Pulls in PR descriptions, comments, and diffs to provide context for informed feedback.
  • Use Case: A developer reviews a PR to confirm it adheres to coding standards before merging.

Quick Start

Review the latest local changes or a PR by URL/ID, for example: "Review PR #123" or "Review changes in src/main.go".

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I automate code reviews for local Git changes and pull requests?

Automated code review targets local working tree changes or remote pull requests by fetching diffs and descriptions to evaluate correctness, maintainability, and security. It uses standard tooling like Git and GitHub CLI to pull historical context for structured feedback.

What is the best way to check if a pull request adheres to project coding standards before merging?

Checking pull request adherence to project standards involves applying a structured evaluation checklist to the fetched PR diffs and comments. This process assesses readability, maintainability, and security to ensure the code meets required quality benchmarks before integration.

Can I review staged Git diffs without pushing to a remote repository?

Reviewing staged Git diffs does not require a remote push; the code review process can identify and target local working tree changes directly. It evaluates the local modifications against project standards to provide immediate, structured feedback.

Does this code review workflow require the GitHub CLI to fetch PR descriptions?

Using the GitHub CLI is required to fetch remote pull request descriptions, comments, and diffs for context-aware evaluation. Standard Git tooling is also utilized to identify and process local code changes effectively.

How do I evaluate a remote pull request by URL or ID?

Evaluating a remote pull request by URL or ID determines the target changes and fetches the corresponding diffs and descriptions. This context is then processed through a structured checklist to assess correctness and maintainability.

What limitations exist when applying a structured checklist to local working tree changes?

Limitations of applying a structured checklist to local changes include lacking remote pull request comments and broader historical context. The review relies solely on staged or working tree diffs, potentially missing project-level discussion threads.