github-code-review

Review local git diffs and GitHub Pull Requests for code issues.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/hochoa13/Asistente-Harlest --skill github-code-review-hochoa13
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-code-review
Source: https://github.com/hochoa13/Asistente-Harlest/tree/main/skills/github/github-code-review
Command: npx skills add https://github.com/hochoa13/Asistente-Harlest --skill github-code-review-hochoa13

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, both locally before pushing and for open Pull Requests on GitHub, ensuring code quality and catching potential issues early.

Core Features & Use Cases

  • Local Code Review: Analyze staged or unstaged changes against a base branch (e.g., main) to identify common issues like debug statements, secrets, or merge conflicts.
  • PR Review: Fetch and analyze open Pull Requests, leave inline comments, and submit formal reviews (Approve, Request Changes).
  • Workflow Integration: Works with gh CLI or falls back to git and the GitHub REST API for maximum compatibility.
  • Use Case: Before pushing your code, ask the agent to perform a pre-push review to catch any last-minute errors. Or, provide a PR number and have the agent analyze it, providing feedback and suggestions directly on GitHub.

Quick Start

Ask the agent to review your local 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 code quality and security issues?

You can review a GitHub Pull Request by fetching the PR changes and analyzing them for correctness, security, and code quality issues. The Skill submits formal reviews with inline comments directly on GitHub using the gh CLI or REST API.

Can I check local git diffs for secrets and debug statements before pushing?

Yes, you can check local git diffs for secrets and debug statements before pushing by comparing staged or unstaged changes against a base branch like main. This pre-push review identifies common issues to ensure local code quality before submission.

Does this code review approach work with the gh CLI or GitHub REST API?

Yes, this code review approach works with the gh CLI and falls back to the git command and GitHub REST API for maximum compatibility. This ensures you can fetch PRs and leave inline comments across different environment setups.

How do I leave inline comments on a GitHub PR?

You leave inline comments on a GitHub PR by fetching the open Pull Request, analyzing the specific code changes, and submitting structured feedback through the gh CLI or GitHub REST API. This provides targeted suggestions directly on the code lines.

What issues are typically identified during an automated code review?

An automated code review typically identifies issues related to correctness, security, code quality, testing, performance, and documentation. It catches common problems like debug statements, secrets, and merge conflicts before code is merged.