github-code-review

Name: github-code-review
Availability: InStock
Author: aissenliu

Review local diffs and GitHub PRs for security and correctness issues.

Updated Apr 27, 2026

Search Tags:#security #github #static-analysis #lint #code-review #pr-review

Ready to run

npx skills add https://github.com/AissenLiu/EasyHermes --skill github-code-review-aissenliu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-code-review
Source: https://github.com/AissenLiu/EasyHermes/tree/main/hermes-agent/skills/github/github-code-review
Command: npx skills add https://github.com/AissenLiu/EasyHermes --skill github-code-review-aissenliu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews are time-consuming and prone to missed issues. This skill provides a structured approach to review local changes or open PRs, suggesting inline comments and a consolidated summary to improve code quality and collaboration.

Core Features & Use Cases

Guides reviewers through local-diff review (git diff main...HEAD) and PR-context review (GitHub PRs via gh/curl).
Generates structured feedback with sections for Critical, Warnings, Suggestions, and Looks Good, plus inline comments mapping to files.
Use cases include pre-merge checks, post-merge audits, and audit-ready PR reviews for high-fidelity projects.

Quick Start

Review the current branch against main and generate a structured code review with inline comments and 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 automate GitHub PR review for security and correctness issues?▼

Automating GitHub PR review involves identifying security and correctness concerns through static analysis of local diffs or PR contexts, generating structured reports with critical issues, warnings, and actionable inline comments for targeted files.

What is the best way to generate structured code review feedback for a local git diff?▼

The best way to generate structured code review feedback for a local git diff is to scope the review to local changes against main, producing a consolidated summary with sections for critical issues, warnings, and suggestions mapped to specific files.

Can I generate inline comments for targeted files during a GitHub code review?▼

Yes, generating inline comments for targeted files during a GitHub code review is supported by leveraging GitHub PR context via gh or curl, mapping structured feedback directly to specific code lines for clear collaboration.

Does this code review approach work for pre-merge checks and post-merge audits?▼

Yes, this code review approach works for pre-merge checks, post-merge audits, and audit-ready reviews by prioritizing stability and security impacts, ensuring high-fidelity project validation across typical PR workflows.

What sections are included in a structured code review summary?▼

A structured code review summary includes sections for Critical issues, Warnings, Suggestions, and a concise Looks Good summary, ensuring actionable reporting that prioritizes concerns impacting codebase stability or security.

Why prioritize security and stability concerns during a static code analysis?▼

Prioritizing security and stability concerns during static code analysis ensures that critical vulnerabilities and correctness issues impacting the codebase are addressed first, streamlining the review process for local changes and open PRs.