github-code-review

Analyze git diffs and GitHub pull requests for actionable code review feedback.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/eddielueng/hermes-agent-zh --skill github-code-review-eddielueng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-code-review
Source: https://github.com/eddielueng/hermes-agent-zh/tree/main/skills/github/github-code-review
Command: npx skills add https://github.com/eddielueng/hermes-agent-zh --skill github-code-review-eddielueng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you catch security, correctness, and quality issues early by reviewing git diffs and GitHub pull requests before you push or merge.

Core Features & Use Cases

  • Pre-push diff review: Analyze staged changes or changes against main to produce a clear verdict-style summary.
  • PR review on GitHub: Fetch PR details, inspect changed files, and leave both summary and inline comments.
  • Inline and formal review actions: Submit APPROVE, REQUEST_CHANGES, or COMMENT using gh or GitHub REST API calls.

Quick Start

Ask the agent to review your local changes by running a pre-push code review against main and returning a Critical/Warnings/Suggestions/Looks Good summary.

Frequently Asked Questions about github-code-review

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

FAQPage Schema
How do I review a git diff for security and correctness issues before pushing?

You can review local git diffs by analyzing staged changes or comparing against the main branch to generate a structured verdict with Critical, Warnings, Suggestions, and Looks Good categories.

Can I leave inline comments on a GitHub pull request automatically?

Yes, you can leave inline comments on a GitHub pull request by fetching PR details, inspecting changed files, and using gh CLI or GitHub REST API calls to submit both summary and inline comments.

How do I submit a formal APPROVE or REQUEST_CHANGES review on GitHub?

To submit formal review actions such as APPROVE, REQUEST_CHANGES, or COMMENT, you use gh CLI or GitHub REST API calls to post the structured review output with inline comment positioning.

Do I need authenticated GitHub access to review pull requests?

Yes, you need authenticated GitHub access to perform PR-level review operations such as fetching PR details and leaving comments, while local pre-push diff reviews only require repository context via git.

What is the best way to catch code quality issues early in the development workflow?

The best way to catch code quality issues early is performing pre-push code reviews on git diffs, allowing you to identify security, correctness, and quality problems before pushing or merging.

Does this code review process work with both local diffs and remote GitHub pull requests?

Yes, the code review process supports both local pre-push workflows by analyzing git diffs and remote PR-level workflows by fetching changes and leaving comments via GitHub REST API or gh CLI.