github-code-review

Automate structured GitHub pull request reviews with inline comments.

13|3|Updated May 12, 2026
One-click install
npx skills add https://github.com/kevinnft/ai-agent-skills --skill github-code-review-kevinnft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-code-review
Source: https://github.com/kevinnft/ai-agent-skills/tree/main/skills/github/github-code-review
Command: npx skills add https://github.com/kevinnft/ai-agent-skills --skill github-code-review-kevinnft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates and standardizes code reviews for GitHub pull requests by guiding users through diff analysis, inline comments, and formal reviews, ensuring consistent feedback across teams.

Core Features & Use Cases

  • Local diff analysis and file-by-file review using git
  • PR-level interactions via gh or REST APIs, including inline comments and formal reviews
  • Structured review outputs with sections for Critical, Warnings, Suggestions, and Looks Good

Quick Start

Begin by selecting a PR to review, fetch it locally, and start your review using the structured guidance.

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 inline code review comments on GitHub pull requests?

You can automate inline code review comments on GitHub pull requests by using this Skill to fetch local diffs and submit structured feedback directly to PRs via gh or REST APIs.

What is the best way to standardize pull request review feedback?

Standardize pull request review feedback by enforcing structured output sections for Critical, Warnings, Suggestions, and Looks Good across all analyzed diffs and inline commentary.

Can I review local git diffs before submitting a formal GitHub PR review?

Yes, you can review local git diffs before submitting a formal GitHub PR review by running local file-by-file diff analysis and then submitting the formal review via gh or curl.

Does this code review workflow support both gh and curl-based API interactions?

Yes, this code review workflow supports both gh and curl-based REST API interactions to manage PR-level operations, inline comments, and formal review submissions.

How do I fetch a pull request locally to start a structured code review?

To start a structured code review, select a target PR, fetch it locally using git, analyze the file-by-file diff, and follow the guided workflow to post inline comments.

When should I use automated inline comments instead of a general PR summary?

Use automated inline comments when you need to provide precise, file-specific feedback on local diffs, reserving general PR summaries for the formal review submission stage.