github-code-review

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

Review local Git diffs and GitHub pull requests for code issues.

Updated Aug 27, 2026

Search Tags:#git #quality assurance #code review #pull request #security #github

Ready to run

npx skills add https://github.com/AXGZ21/hermes-agent-railway --skill github-code-review-axgz21

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of reviewing code changes, whether they are local pre-push commits or open pull requests on GitHub, ensuring code quality, security, and adherence to best practices.

Core Features & Use Cases

Local Code Review: Analyze staged or unstaged changes against a base branch (e.g., main) to identify potential issues before committing or pushing.
Pull Request Review: Fetch and analyze open PRs, providing detailed feedback and optionally leaving inline comments or submitting formal reviews (approve, request changes).
Automated Checks: Identifies common issues like debug statements, secrets, merge conflicts, and security vulnerabilities.
Use Case: Before pushing a new feature, ask the agent to "review my local changes for any critical issues." Or, when a teammate opens a PR, ask the agent to "review PR #123 on the main repository."

Quick Start

Ask the agent to review your local code changes against the main branch.

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 security and quality issues?▼

To review a GitHub pull request, fetch the PR diff using GitHub CLI or REST API, then analyze the changes for correctness, security vulnerabilities, and quality issues. This Skill automates that process and can submit formal reviews or inline comments directly.

Can I check my local Git diff for potential issues before pushing?▼

Yes, you can check a local Git diff by comparing staged or unstaged changes against a base branch like main using standard Git commands. This identifies debug statements, secrets, and security vulnerabilities before you commit or push.

Does automated code review work with the GitHub CLI?▼

Automated code review works with the GitHub CLI by integrating with its commands and the REST API for pull request interactions. This allows fetching PR details and submitting formal feedback like approval or change requests directly through the interface.

What is the best way to find secrets and debug statements in a Git diff?▼

The best way to find secrets and debug statements in a Git diff is to perform automated checks against local changes. This process scans the codebase for common issues like hardcoded secrets, merge conflicts, and security vulnerabilities before integration.

What are the limitations of reviewing local Git changes against a base branch?▼

Reviewing local Git changes against a base branch is limited to analyzing staged or unstaged diffs using standard Git commands. It cannot submit formal reviews or inline comments to GitHub directly, which requires CLI or REST API integration for open pull requests.