github-code-review

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

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/kaminocorp/hermes-alpha-hunter --skill github-code-review-kaminocorp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-code-review
Source: https://github.com/kaminocorp/hermes-alpha-hunter/tree/main/skills/github/github-code-review
Command: npx skills add https://github.com/kaminocorp/hermes-alpha-hunter --skill github-code-review-kaminocorp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Reviewing code changes before pushing or evaluating open pull requests is time-consuming and error-prone, and posting structured feedback with inline comments on GitHub requires tedious manual API or CLI work. ## Core Features & Use Cases - Pre-Push Local Review: Analyze staged or branch diffs with plain git, scanning for debug statements, secrets, conflict markers, and common code issues. - Pull Request Review: Fetch PR details, check out PR branches locally, run tests and linters, then submit formal reviews (approve, request changes, or comment) via gh CLI or the GitHub REST API with curl. - Structured Feedback: Post inline review comments and severity-tagged summary comments (Critical, Warnings, Suggestions, Looks Good) using a consistent output template. - Use Case: A teammate asks you to review PR #123. The skill checks out the PR, reads the diff, runs the test suite, applies a review checklist covering correctness, security, and testing, then posts an atomic review with inline comments and a summary verdict. ## Quick Start Review the open pull request number 123 in this repository and post your findings as inline comments and a summary review 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/123/head:pr-123 and check it out, then inspect the diff with git diff main...HEAD. Submit the review using gh pr review or a POST to the GitHub reviews API endpoint.

How to review local git changes before pushing?▼

Run git diff main...HEAD --stat for scope, then read the full diff and grep for debug statements, secrets, and conflict markers. Present findings grouped by severity: critical issues, warnings, suggestions, and positive observations.

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 PR comments, inline review comments, and formal review submissions through the GitHub REST API.

How do I leave inline comments on specific lines of a pull request?▼

Get the PR head commit SHA, then POST to the pulls comments endpoint with the file path, line number, commit_id, and side set to RIGHT. Multiple comments can be submitted atomically as part of a formal review.

What should a code review checklist cover?▼

A thorough review checks correctness and edge cases, security issues like hardcoded secrets and injection risks, code quality and naming, test coverage, performance problems like N+1 queries, and documentation of public APIs.