github-code-review

Review GitHub code changes for defects, security risks, and improvements.

3|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/twjarviszyra-web/hermes-unbound --skill github-code-review-twjarviszyra-web
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-code-review
Source: https://github.com/twjarviszyra-web/hermes-unbound/tree/main/skills/github/github-code-review
Command: npx skills add https://github.com/twjarviszyra-web/hermes-unbound --skill github-code-review-twjarviszyra-web

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you catch bugs, security risks, and design issues in code changes before they are merged or pushed.

Core Features & Use Cases

  • Local change review: Analyze git diffs, staged work, and branch changes before a push.
  • Pull request review: Inspect PR details, review changed files, and leave inline or summary comments on GitHub.
  • Quality checklist: Evaluate correctness, security, testing, performance, and documentation in a structured way.
  • Use case: If a teammate opens a PR or you are about to push a feature branch, use this Skill to produce a clear review with critical issues, warnings, suggestions, and positives.

Quick Start

Ask me to review the current branch or a GitHub pull request, and I will summarize the findings with actionable feedback.

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 risks?

Reviewing a GitHub pull request for bugs and security risks requires collecting diffs via git history, the gh CLI, or GitHub REST API, then evaluating correctness, security, testing, performance, and documentation to produce actionable inline comments and formal feedback.

Can I analyze local git diffs before pushing a branch to GitHub?

Analyzing local git diffs before pushing a branch allows you to catch design issues and defects early. The Skill inspects staged work and branch changes locally, summarizing critical issues, warnings, and suggestions before code reaches remote repositories.

Do I need the gh CLI to inspect pull requests and leave inline comments?

Inspecting pull requests and leaving inline comments requires git history, the gh CLI, or GitHub REST API access via curl. These dependencies collect diffs, comment on files, and submit formal reviews on GitHub.

What is the best way to structure code review feedback for changed files?

The best way to structure code review feedback for changed files is applying a quality checklist that evaluates correctness, security, testing, performance, and documentation, generating clear summaries with critical issues, warnings, suggestions, and positives.

Are there limitations when using curl to collect diffs and submit formal reviews?

Limitations when using curl to collect diffs and submit formal reviews include requiring GitHub REST API access and proper authentication. The Skill relies on git history, the gh CLI, or curl to collect diffs, comment on files, and submit formal reviews.

Why should I use automated quality assurance for pre-push branch reviews?

Automated quality assurance for pre-push branch reviews identifies defects and security risks before changes are merged. It evaluates local git diffs against a structured checklist, providing actionable feedback to improve code quality before integration.