github-code-review

Reviews local git diffs and GitHub pull requests with inline comments via gh or REST API.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/vivekgoquest/hermes-agent-stable --skill github-code-review-vivekgoquest
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-code-review
Source: https://github.com/vivekgoquest/hermes-agent-stable/tree/main/skills/github/github-code-review
Command: npx skills add https://github.com/vivekgoquest/hermes-agent-stable --skill github-code-review-vivekgoquest

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 common issues, and posting structured feedback on GitHub, which is repetitive and error-prone. ## Core Features & Use Cases - Local Pre-Push Review: Analyze staged or branch diffs with plain git, scanning for debug statements, secrets, conflict markers, and oversized files. - Full PR Review Workflow: Fetch PR metadata, check out the PR branch locally, run tests and linters, then submit formal reviews (approve, request changes, or comment) with inline comments. - Dual Tooling Support: Works with either the gh CLI or plain git plus curl against the GitHub REST API, so it functions even without gh installed. - Use Case: A teammate asks you to review PR #123. The skill checks out the branch, runs the test suite, applies a correctness/security/testing checklist, and posts an atomic review with severity-tagged inline comments plus a summary comment. ## Quick Start Review pull request number 123 in this repository and post inline comments with a summary of any critical issues found.

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/N/head:pr-N and check it out, then diff against the base branch. Use gh pr review or the GitHub REST API reviews endpoint to submit approval, change requests, or inline comments.

How to add inline comments to a GitHub PR via API?▼

POST to the pulls/N/comments endpoint with the file path, line number, head commit SHA, and comment body. For multiple comments, submit them atomically through the pulls/N/reviews endpoint with an event of APPROVE, REQUEST_CHANGES, or COMMENT.

Can I review GitHub PRs without the gh CLI installed?▼

Yes, plain git handles fetching and diffing PR branches, and curl with a GITHUB_TOKEN covers all API interactions like comments and reviews. The token can come from the environment, a .env file, or git credentials.

What should I check when reviewing code before pushing?▼

Run git diff main...HEAD and scan for leftover debug statements, hardcoded secrets, merge conflict markers, and accidentally staged large files. Then apply a checklist covering correctness, security, code quality, testing, performance, and documentation.

When should I request changes versus approve a pull request?▼

Request changes when any critical or warning-level issue exists, such as security vulnerabilities or missing error handling. Approve when only minor suggestions remain, and use a plain comment review for draft PRs or uncertain findings.