skills.rest
ewtodd
ewtoddCOMMUNITY
Explore all skills by this author →
GitHub

github-code-review

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

Updated Aug 21, 2026
Search Tags:#code review#pull request#github#gh cli#rest api#git diff#inline comments
One-click install
npx skills add https://github.com/ewtodd/son-of-anton --skill github-code-review-ewtodd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-code-review
Source: https://github.com/ewtodd/son-of-anton/tree/main/skills/github/github-code-review
Command: npx skills add https://github.com/ewtodd/son-of-anton --skill github-code-review-ewtodd

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; this Skill standardizes that entire workflow with ready-to-run git, gh, and curl commands. ## Core Features & Use Cases - Local Pre-Push Review: Inspect staged or branch diffs with plain git, scan for debug statements, secrets, and conflict markers, and present findings in a structured Critical/Warning/Suggestion format. - Full PR Review: Fetch PR metadata, check out the PR branch locally, run tests and linters, then submit formal reviews (approve, request changes, comment) with inline comments via gh or the GitHub REST API. - Use Case: A teammate opens PR #123 touching authentication code. You check out the branch, run the test suite, spot a SQL injection on line 45, and submit a REQUEST_CHANGES review with an inline comment plus a summary comment — all in one flow. ## Quick Start Review pull request 123 in this repository and post your findings as inline comments and a 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 from the command line?▼

Fetch the PR branch with git fetch origin pull/123/head:pr-123, check it out, then inspect the diff with git diff main...HEAD. Use gh pr view and gh pr diff for metadata, or the GitHub REST API with curl if gh is unavailable.

How to add inline comments to a GitHub PR review?▼

Post to the pulls/comments endpoint with the file path, line number, commit SHA, and body, using gh api or curl. For multiple comments, submit one review to the pulls/reviews endpoint with an event of APPROVE, REQUEST_CHANGES, or COMMENT.

Can I review code without the gh CLI installed?▼

Yes, local diff review uses plain git only, and all PR interactions work through the GitHub REST API with curl and a GITHUB_TOKEN. The token can come from the environment, a .env file, or git credentials.

What should a code review checklist cover?▼

Check correctness and edge cases, security issues like hardcoded secrets and injection, code quality and duplication, test coverage, performance problems like N+1 queries, and documentation of public APIs and non-obvious logic.

When should I request changes versus approve a pull request?▼

Approve when only minor suggestions remain and no critical or warning issues exist. Request changes when any critical or warning-level issue must be fixed before merge, and use comment-only reviews for drafts or uncertain findings.

Related Skills

Explore More Software Engineering Skills→
specdogspecdog

github-code-review

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

Official
Intermediate
roycolumbia-coderoycolumbia-code

gsd-ship

Automates GitHub pull request creation, review triggering, and merge tracking.

Community
Intermediate
staticalandstaticaland
4

create-pr

Creates GitHub pull requests with structured descriptions generated from full session context.

Community
Intermediate
MatthieuszMatthieusz

plannotator-annotate

Launch Plannotator's browser-based annotation UI from the command line.

Community
Basic