github-code-review

Review local git diffs and GitHub pull requests with inline comments via gh or REST API.

1|Updated Aug 6, 2026
One-click install
npx skills add https://github.com/agtktID/indagis-agent --skill github-code-review-agtktid
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-code-review
Source: https://github.com/agtktID/indagis-agent/tree/main/skills/github/github-code-review
Command: npx skills add https://github.com/agtktID/indagis-agent --skill github-code-review-agtktid

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Reviewing code changes before pushing or evaluating open pull requests requires juggling diffs, context, and GitHub's review APIs manually, which is slow and error-prone. This Skill provides a structured workflow for inspecting changes, applying a systematic review checklist, and posting formal reviews with inline comments back to GitHub. ## Core Features & Use Cases - Pre-Push Local Review: Analyze staged or branch diffs with plain git, scanning for debug statements, secrets, merge conflict markers, and oversized files before pushing. - End-to-End PR Review: Fetch PR metadata, check out the PR branch locally, run tests and linters, then submit an atomic review (APPROVE, REQUEST_CHANGES, or COMMENT) with inline comments. - Dual Auth Paths: Works with the gh CLI when available, or falls back to curl with a GITHUB_TOKEN against the GitHub REST API. - Use Case: A teammate opens PR #123 touching authentication code. Ask the agent to review it — it checks out the branch, runs pytest, flags a SQL injection at src/auth.py:45 as critical, and posts a structured summary comment with severity-tagged inline notes. ## Quick Start Review PR #123 in this repository and post inline comments for any critical issues you find.

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 from the command line?▼

Fetch the PR branch with git fetch origin pull/123/head:pr-123, check it out, and inspect the diff against the base branch. Then submit a formal review with gh pr review or by posting to the GitHub reviews REST endpoint with inline comments.

How to add inline comments to a GitHub PR via API?▼

Post to /repos/{owner}/{repo}/pulls/{number}/comments with the body, file path, head commit SHA, line number, and side. For multiple comments, submit them atomically through the /reviews endpoint with an event of APPROVE, REQUEST_CHANGES, or COMMENT.

Can I review code without the gh CLI installed?▼

Yes, all PR interactions work with plain git plus curl against the GitHub REST API using a GITHUB_TOKEN. Local pre-push reviews need only git commands like git diff main...HEAD, with no API access required.

What does the code review checklist cover?▼

The checklist covers six categories: correctness, security, code quality, testing, performance, and documentation. It includes automated greps for leftover debug statements, hardcoded secrets, and merge conflict markers in the diff.

When should a review request changes instead of approving?▼

Request changes when any critical or warning-level issue exists, such as security vulnerabilities or missing error handling. Approve when only minor suggestions remain, and use comment-only reviews for draft PRs or uncertain findings.