github-code-review

Review local git changes and GitHub pull requests with automated diff analysis.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, curl, python3, git, and includes references (resource) components.

What problem does it solve?

This skill addresses the cognitive load and time-consuming nature of manual code reviews by providing a structured, automated framework for analyzing diffs, identifying security vulnerabilities, and managing pull request feedback.

Core Features & Use Cases

  • Local Pre-Push Analysis: Automatically scan staged changes for secrets, debug statements, and common code quality issues before code ever leaves your machine.
  • End-to-End PR Workflow: Manage the entire lifecycle of a GitHub pull request, from fetching and checking out branches to submitting formal, atomic reviews with inline comments.
  • Standardized Review Checklist: Apply a consistent, professional rubric covering correctness, security, performance, and documentation to every review.

Quick Start

Use the github-code-review skill to analyze the current pull request number 123 and provide a summary of findings.

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 code reviews for GitHub pull requests?

Automate GitHub pull request reviews by fetching remote branches, analyzing diffs for security vulnerabilities and quality issues, and submitting formal inline comments via the GitHub API. This structured framework analyzes changes and posts feedback directly to the pull request.

Can I scan local git changes for secrets before pushing to GitHub?

Yes, you can scan local staged git changes for secrets, debug statements, and code quality issues before pushing. This pre-push analysis prevents sensitive data exposure by evaluating diffs locally before code leaves your machine.

What do I need to run automated PR reviews and check out remote branches?

Running automated PR reviews requires authenticated GitHub access via the `gh` CLI or personal access tokens. You also need `python3`, `curl`, and `git` installed to fetch branches, execute diff analysis, and submit review comments.

What is the best way to apply a consistent checklist to pull request diff analysis?

The best way to apply consistent pull request diff analysis is using a standardized review rubric. This evaluates correctness, security, performance, and documentation across every review, ensuring comprehensive quality assurance and structured collaborative feedback.

Does the automated code review process submit formal comments directly to GitHub?

Yes, the automated code review process submits formal, atomic reviews with inline comments directly to GitHub. It manages the entire pull request lifecycle through API-driven interactions after completing the local diff analysis.

When should I not use automated code review for my git workflow?

Automated code review may not suit workflows lacking authenticated GitHub access or required dependencies like `python3` and `gh`. It also has limitations with complex architectural changes where automated diff analysis cannot fully replace human contextual judgment.