github-code-review

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

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/swcstudiospace/aimeecodes --skill github-code-review-swcstudiospace
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-code-review
Source: https://github.com/swcstudiospace/aimeecodes/tree/main/.aimee/skills/github-code-review
Command: npx skills add https://github.com/swcstudiospace/aimeecodes --skill github-code-review-swcstudiospace

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 APIs manually. This Skill provides a structured workflow for inspecting changes, applying a consistent review checklist, and posting inline comments or formal reviews to GitHub. ## Core Features & Use Cases - Local Pre-Push Review: Analyze staged or branch diffs with plain git, scanning for debug statements, secrets, merge conflict markers, and oversized files. - Full PR Review Workflow: Fetch PR metadata, check out the PR branch locally, run tests and linters, then submit an approve, request-changes, or comment review. - Inline Comments via gh or curl: Post single inline comments or atomic multi-comment reviews using either the GitHub CLI or the REST API with a token. - Use Case: A teammate asks you to review PR #123. The Skill checks out the branch, reads each changed file with full context, runs the test suite, then posts a structured summary comment with severity-tagged inline findings. ## Quick Start Ask the agent to review PR number 123 in the current repository and post the findings as inline comments on GitHub.

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 with git diff main...HEAD. Then submit a formal review using gh pr review or the GitHub REST API reviews endpoint.

How to post inline comments on a GitHub PR without the gh CLI?▼

Use curl against the GitHub REST API pulls comments endpoint with your token, the head commit SHA, file path, and line number. Multiple comments can be submitted atomically through the reviews endpoint with an event of APPROVE, REQUEST_CHANGES, or COMMENT.

What is the difference between gh pr review and the REST API reviews endpoint?▼

gh pr review is a simpler CLI shortcut for approving or requesting changes with a body message. The REST API reviews endpoint supports atomic submission of multiple inline comments together with the review verdict in a single request.

Does this code review workflow work without GitHub authentication?▼

Local pre-push review works entirely with plain git and needs no authentication. PR-level interactions like viewing details or posting comments require either an authenticated gh session or a GITHUB_TOKEN environment variable.

When should I request changes instead of approving a pull request?▼

Request changes when the review finds any critical or warning-level issue such as security vulnerabilities, missing error handling, or absent tests for new code. Approve when only minor suggestions remain, and use comment for draft PRs or uncertain findings.