github-code-review

Review git diffs and GitHub pull requests with inline comments and structured feedback.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Reviewing code changes before pushing or evaluating open pull requests requires manually reading diffs, checking for security issues, and posting feedback on GitHub, which is time-consuming and error-prone. ## Core Features & Use Cases - Pre-Push Local Review: Analyze staged or branch diffs with plain git commands, scanning for debug statements, secrets, merge conflict markers, and oversized files. - Pull Request Review: Fetch PR details, check out PR branches locally, run tests and linters, then submit formal reviews (approve, request changes, or comment) with inline comments via gh CLI or the GitHub REST API. - Structured Feedback: Apply a systematic checklist covering correctness, security, code quality, testing, performance, and documentation, with severity-rated output (Critical, Warnings, Suggestions, Looks Good). - Use Case: A teammate asks you to review PR #42. The skill checks out the PR, reads the diff, runs the test suite, identifies a SQL injection vulnerability, and posts a request-changes review with inline comments and a summary comment. ## Quick Start Review the open pull request number 123 in this repository and post your findings as inline comments on GitHub.

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 GitHub pull request from the command line?

Fetch the PR branch with git fetch origin pull/NUMBER/head:pr-NUMBER and check it out, then run git diff main...HEAD to read the changes. Submit feedback with gh pr review or by posting to the GitHub reviews API endpoint.

How to review local git changes before pushing?

Run git diff main...HEAD --stat for scope, then git diff main...HEAD for the full diff. Grep the diff for debug statements, secrets, and conflict markers, then present findings grouped by severity: critical, warnings, and suggestions.

Can I leave inline comments on a GitHub PR without the gh CLI?

Yes, use curl with a GITHUB_TOKEN to POST to the pulls/NUMBER/comments endpoint, providing the body, file path, head commit SHA, line number, and side. The same API supports multi-comment atomic reviews via the reviews endpoint.

Does this code review workflow work without GitHub CLI installed?

Yes, all PR interactions have curl-based fallbacks using the GitHub REST API with a token read from GITHUB_TOKEN, ~/.hermes/.env, or ~/.git-credentials. Local diff review uses plain git and needs no API access.

When should I approve versus request changes on a PR review?

Approve when there are no critical or warning-level issues, only minor suggestions. Request changes when any critical or warning issue exists, such as security vulnerabilities or missing error handling. Use comment-only reviews for draft PRs or uncertain findings.