github-code-review

Analyze and annotate code changes in GitHub pull requests or local diffs.

31|3|Updated May 7, 2026
One-click install
npx skills add https://github.com/markwang2658/hermes-windows-native --skill github-code-review-markwang2658
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-code-review
Source: https://github.com/markwang2658/hermes-windows-native/tree/main/hermes-agent/skills/github/github-code-review
Command: npx skills add https://github.com/markwang2658/hermes-windows-native --skill github-code-review-markwang2658

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review is time-consuming and error-prone when assessing diffs across GitHub PRs or local changes; this skill provides a structured mechanism to identify issues, propose fixes, and improve code quality.

Core Features & Use Cases

  • Inline review comments: Generate precise feedback tied to changed files and lines.
  • PR-to-PR consistency: Ensure standards are met across multiple PRs with a single workflow.
  • Formal review output: Produce a structured summary suitable for code-review tooling.

Quick Start

Run the code-review skill on a local Git repository to produce structured feedback for the latest changes.

Frequently Asked Questions about github-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate structured code review comments for GitHub pull requests?

To generate code review comments for GitHub pull requests, you can apply this skill to parse PR diffs and produce inline suggestions tied to changed files and lines. It outputs severity-based findings and a formal review summary.

Can I review local Git diffs or does it only work with GitHub PRs?

You can review local Git diffs as well as GitHub PRs. The skill analyzes local code changes to produce structured feedback, inline comments, and severity-based findings using the same formal review workflow.

What is the best way to ensure review consistency across multiple pull requests?

The best way to ensure consistency across multiple pull requests is to use a single structured review workflow that applies standardized parsing and severity-based findings to every PR diff, generating formal summaries and inline suggestions.

How does automated diff parsing improve code quality and safety?

Automated diff parsing improves code quality by analyzing code changes to identify issues and generate severity-based findings. It provides structured inline suggestions and a top-level summary to highlight safety concerns.

Do I need any external dependencies to run code review on a local repository?

No external dependencies are required to run code review on a local repository. You can run the skill directly on your local Git repository to analyze the latest changes and produce structured feedback.

What format do the code review outputs take for integration with review tooling?

Code review outputs take the format of a formal structured summary accompanied by inline review comments. This format is designed to be suitable for integration with code-review tooling.