github-code-review

Extract GitHub PR diffs and post inline comments via gh CLI or REST.

2|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/john-data-chen/hermes-agent-backup --skill github-code-review-john-data-chen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-code-review
Source: https://github.com/john-data-chen/hermes-agent-backup/tree/main/skills/github/github-code-review
Command: npx skills add https://github.com/john-data-chen/hermes-agent-backup --skill github-code-review-john-data-chen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines code review by automating the retrieval and analysis of diffs and by enabling precise inline comments on GitHub PRs, reducing manual review time and improving consistency.

Core Features & Use Cases

  • Review local changes vs main by generating and inspecting diffs, including per-file changes and summary statistics.
  • Review open PRs on GitHub using the gh CLI or REST endpoints, fetch PR metadata, and attach inline comments or formal reviews.
  • Produce structured feedback in a consistent format that helps teams maintain code quality and clarity during code reviews.

Quick Start

Review a PR by fetching its details, diffing changes, and posting inline comments.

Frequently Asked Questions about github-code-review

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

FAQPage Schema
How do I automate GitHub pull request reviews with inline comments?

Automate GitHub pull request reviews by extracting diffs and attaching inline comments directly to the code. This skill uses the gh CLI or REST API to fetch PR metadata and post structured feedback.

Can I review local git diffs against main before opening a pull request?

Yes, you can review local git diffs against the main branch. The skill generates and inspects per-file changes and summary statistics for local modifications before they are committed to a remote pull request.

Do I need a GitHub access token to review open pull requests?

A GitHub access token is required to review open pull requests. You also need a local Git repository and standard tooling like the gh CLI or a REST client to authenticate and interact with the API.

What is the best way to structure code review feedback for GitHub PRs?

The best way to structure code review feedback is by producing consistent, formatted output for inline comments. This ensures teams maintain code quality and clarity during reviews without manual formatting.

Does this code review skill work with both the gh CLI and REST API workflows?

This code review skill works with both the gh CLI and REST API workflows. It supports fetching PR details and posting formal reviews using either command-line interface tools or direct API endpoints.

When should I not use automated inline comments for code reviews?

Automated inline comments might not be suitable when manual discussion is needed or if standard tooling like gh CLI is unavailable. The process requires a Git repository and proper API authentication to function.