github-code-review

Reviews Git diffs and GitHub PRs for bugs, security risks, and maintainability issues before integration.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers identify bugs, security issues, quality problems, and missing tests before code is merged by providing a structured code review workflow for local changes and GitHub pull requests.

Core Features & Use Cases

  • Local Change Reviews: Analyze git diffs, inspect changed files, and check for common correctness, security, and maintainability issues before pushing.
  • Pull Request Reviews: Review GitHub PR metadata, diffs, changed files, and submit comments or formal review decisions using gh or REST APIs.
  • Review Standards: Apply consistent checks for correctness, security, testing, performance, and documentation quality across code changes.
  • Use Case: A developer preparing a pull request can use this Skill to review the branch, find potential SQL injection risks or missing tests, and prepare actionable feedback for the team.

Quick Start

Ask the github-code-review skill to review my current branch changes and summarize any critical issues, warnings, and suggestions.

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 GitHub pull requests for security risks and defects?

Reviewing GitHub pull requests for security risks and defects involves analyzing source code diffs, inspecting changed files, and checking for correctness, maintainability, and missing tests before integration. This Skill applies consistent checks across code changes to identify bugs, SQL injection risks, and quality problems.

How do I check local git diffs for bugs before pushing a branch?

Checking local git diffs for bugs before pushing a branch requires analyzing local changes and inspecting changed files for common correctness, security, and maintainability issues. This Skill provides a structured workflow to review local changes and summarize critical issues, warnings, and suggestions.

What is the best way to automate code review for GitHub workflows?

Automating code review for GitHub workflows involves inspecting pull request metadata, diffs, and changed files, then submitting comments or formal review decisions via gh or REST APIs. This Skill applies consistent review standards for correctness, security, testing, performance, and documentation quality across code changes.

Can I submit formal review decisions and inline comments on GitHub PRs?

Submitting formal review decisions and inline comments on GitHub PRs is supported through optional gh or GitHub REST API interactions for pull request management. This Skill enables reviewing PR metadata and diffs, then submitting actionable feedback or formal review decisions directly to the repository.

Does this code review process require specific GitHub API tokens or dependencies?

This code review process requires git-based change analysis for local diffs and pull request inspection. Optional gh or GitHub REST API interactions are needed for pull request management, such as submitting formal review decisions and inline comments, but no specific external dependencies are mandated.

What types of maintainability issues can code review identify in source code changes?

Code review can identify maintainability issues in source code changes by applying consistent checks for correctness, security, testing, performance, and documentation quality. This Skill helps developers find potential SQL injection risks, missing tests, and other quality problems before code is merged.