github-code-review

Reviews Git diffs and GitHub PRs for correctness, security, code quality, testing gaps, and performance issues.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/JKhyro/HERMES-AGENT --skill github-code-review-jkhyro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-code-review
Source: https://github.com/JKhyro/HERMES-AGENT/tree/main/skills/github/github-code-review
Command: npx skills add https://github.com/JKhyro/HERMES-AGENT --skill github-code-review-jkhyro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the friction of manual code review by helping you inspect diffs, spot bugs and security issues, and turn findings into clear review feedback before a push or during a pull request.

Core Features & Use Cases

  • Local change review: Analyze staged work or a branch diff before pushing to catch regressions early.
  • PR review workflow: Inspect GitHub pull requests, summarize scope, and leave general or inline comments.
  • Structured feedback: Organize review results into Critical, Warnings, Suggestions, and Looks Good so the author can act quickly.
  • Use case: A developer asks for a pre-merge review on a feature branch, and this Skill checks the diff, validates risks, and formats a review ready to post back on GitHub.

Quick Start

Use the github-code-review skill to review my current branch for bugs, security issues, and missing tests, then summarize the findings in a structured review.

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 for bugs and security issues?

You can review a GitHub pull request by analyzing the diff to identify bugs, security issues, and testing gaps, then generating structured feedback categorized by severity to validate risks before merging.

Can I check my local git diff for code quality before pushing?

Yes, you can check your local git diff for code quality before pushing by analyzing staged work or branch diffs. This pre-push review helps catch regressions, performance issues, and missing tests early in the development cycle.

How do I leave inline comments on a GitHub pull request automatically?

You can leave inline comments on a GitHub pull request automatically by using the gh CLI or GitHub REST API to submit review feedback. This allows you to post targeted review results directly to specific lines of code in the PR.

Do I need the gh CLI to review pull requests?

You do not strictly need the gh CLI to review pull requests; it is optional. You can use git access for local diff analysis, and optionally use the gh CLI or GitHub REST API via curl for PR metadata retrieval and review submission.

What is the best way to structure code review feedback?

The best way to structure code review feedback is to organize findings into distinct categories like Critical, Warnings, Suggestions, and Looks Good. This format helps the author quickly understand the scope and prioritize actions for approval decisions.