github-code-review

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

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/luckybbjason1/trading --skill github-code-review-luckybbjason1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-code-review
Source: https://github.com/luckybbjason1/trading/tree/main/.hermes/skills/github/github-code-review
Command: npx skills add https://github.com/luckybbjason1/trading --skill github-code-review-luckybbjason1

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 juggling git diffs, GitHub API calls, and structured feedback formatting, which is tedious and error-prone when done manually. ## Core Features & Use Cases - Pre-Push Local Review: Analyze staged or branch diffs with plain git, scanning for debug statements, secrets, merge conflict markers, and oversized files. - End-to-End PR Review: 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 via gh CLI or curl. - Structured Feedback Format: Present findings using a severity-tiered template (Critical, Warnings, Suggestions, Looks Good) defined in the references template. - Use Case: A teammate asks you to review PR #123. The skill checks out the branch, runs the test suite, applies a six-category checklist (correctness, security, quality, testing, performance, documentation), and posts an atomic multi-comment review to GitHub. ## Quick Start Ask the agent to review PR number 123 in the current repository and post inline comments with a 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 GitHub pull request from the command line?

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

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

POST to /repos/{owner}/{repo}/pulls/{number}/comments with the body, file path, commit_id of the PR head SHA, line number, and side. You can also batch multiple inline comments into one atomic review via the /reviews endpoint.

Can I review code without the gh CLI installed?

Yes, all PR interactions work with plain git plus curl against the GitHub REST API using a GITHUB_TOKEN. Local pre-push reviews need only git commands like git diff main...HEAD.

What should a code review checklist include?

Cover six categories: correctness and edge cases, security issues like hardcoded secrets and injection, code quality and naming, test coverage, performance concerns like N+1 queries, and documentation of public APIs.

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 comment-only reviews for draft PRs or uncertain findings.