github-code-review

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

115|9|Updated Aug 5, 2026
One-click install
npx skills add https://github.com/AtlasOmnia/donna-starter --skill github-code-review-atlasomnia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-code-review
Source: https://github.com/AtlasOmnia/donna-starter/tree/main/skills/github/github-code-review
Command: npx skills add https://github.com/AtlasOmnia/donna-starter --skill github-code-review-atlasomnia

SYSTEM DOCUMENTATION & REQUIREMENTS

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 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, conflict markers, and oversized files. - End-to-End PR Review: Fetch PR metadata, check out the PR branch locally, run tests and linters, then submit an approve/request-changes/comment review with inline comments via gh or curl. - Structured Feedback Format: Findings are organized into Critical, Warnings, Suggestions, and Looks Good sections, plus a whole-repo health evaluation mode. - Use Case: Ask the agent to "review PR #123" and it checks out the branch, runs the test suite, applies the review checklist, and posts an atomic multi-comment review to GitHub. ## Quick Start Ask the agent to review pull request 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 and check it out, then inspect the diff with git diff main...HEAD. Use gh pr review or the GitHub REST API to submit an approve, request-changes, or comment review with inline comments.

How to add inline comments to a GitHub PR using the API?

POST to /repos/{owner}/{repo}/pulls/{number}/comments with the body, file path, head commit SHA, line number, and side. Alternatively submit multiple comments atomically via the /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 curl against the GitHub REST API using a GITHUB_TOKEN environment variable. The gh CLI is a convenience, not a requirement.

What should a code review checklist cover?

A thorough review checks correctness and edge cases, security issues like hardcoded secrets and injection risks, code quality and duplication, test coverage, performance problems like N+1 queries, and documentation of public APIs.

Why can't tests be verified during an automated PR review?

Test execution can be blocked by unresolved dependencies, missing build tools, or failed installs. In that case the review should report the concrete blocker and treat test presence as a positive signal without claiming the suite passes.