github-code-review

Review git diffs and GitHub pull requests for defects and security issues.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/Gitnapp/Skills --skill github-code-review-gitnapp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-code-review
Source: https://github.com/Gitnapp/Skills/tree/main/github/github-code-review
Command: npx skills add https://github.com/Gitnapp/Skills --skill github-code-review-gitnapp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers identify bugs, security risks, quality issues, and improvement opportunities in local changes or GitHub pull requests before code is merged.

Core Features & Use Cases

  • Local Change Reviews: Analyze git diffs, inspect modified files, and provide structured feedback on correctness, security, testing, performance, and maintainability.
  • Pull Request Reviews: Review GitHub PR metadata, changed files, inline comments, and formal review states using gh CLI or GitHub REST APIs.
  • Use Case: A developer preparing a release can use this Skill to review a pull request, identify blocking issues, and generate actionable comments before merging.

Quick Start

Ask the GitHub code review skill to review the current branch changes and provide a structured code review summary.

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 issues before merging?

To review a GitHub pull request for security issues and defects, you can analyze modified files, inspect metadata, and generate structured feedback on correctness and maintainability before merging.

Can I review local git diffs without pushing to GitHub?

You can review local git diffs without GitHub by analyzing modified files in your current branch to identify correctness, security, testing, performance, and maintainability problems directly.

What's the best way to automate code review feedback on GitHub pull requests?

Automating code review feedback on pull requests involves inspecting changed files and metadata through gh CLI or REST APIs to generate actionable comments and formal review states.

Do I need GitHub authentication to review pull request changes?

GitHub authentication through gh CLI or REST API interactions is required for PR-level operations like reading metadata, inline comments, and formal review states.

Does the code review process work with local git workflows?

The code review process works with local git workflows by inspecting local diffs and modified files to provide structured feedback on software quality without requiring remote access.

What types of maintainability problems can be found during a code review?

During a code review, maintainability problems are identified alongside defects, security risks, and performance issues by analyzing git diffs and modified files to ensure software quality before merging.