github-code-review

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

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/AvaTar-ArTs/.Agent-skills --skill github-code-review-avatar-arts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-code-review
Source: https://github.com/AvaTar-ArTs/.Agent-skills/tree/main/skills/github/github-code-review
Command: npx skills add https://github.com/AvaTar-ArTs/.Agent-skills --skill github-code-review-avatar-arts

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, which is slow and error-prone. 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 - Pre-Push Local Review: Analyze staged or branch diffs with plain git, scanning for debug statements, secrets, conflict markers, and oversized files before pushing. - Full PR Review Workflow: Fetch PR metadata, check out the PR branch locally, run tests and linters, then submit an atomic review with inline comments via gh CLI or the GitHub REST API. - Structured Feedback Format: Present findings using a severity-tiered template (Critical, Warnings, Suggestions, Looks Good) with a clear approve/request-changes/comment decision rule. - 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 inline comments on specific lines plus a summary comment with a verdict. ## Quick Start Ask the agent to review pull request number 123 in the current repository and post inline comments with a summary verdict.

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?

Use gh pr view and gh pr diff to inspect the PR, then git fetch origin pull/N/head:pr-N to check it out locally for full context. Submit feedback with gh pr review --approve, --request-changes, or --comment, or post inline comments via the GitHub REST API.

How do I review local changes before pushing to GitHub?

Run git diff main...HEAD to see the full diff and git diff main...HEAD --stat for scope. Grep the diff for debug statements, secrets, and conflict markers, then present findings grouped by severity: critical, warnings, suggestions, and looks good.

How do I add inline comments to a GitHub PR with curl?

Fetch the PR head commit SHA from the pulls endpoint, then POST to /repos/{owner}/{repo}/pulls/{number}/comments with body, path, commit_id, line, and side fields. For multiple comments, submit one review to the /reviews endpoint with a comments array.

Does this work without the gh CLI installed?

Yes. All PR interactions have curl-based equivalents using the GitHub REST API with a GITHUB_TOKEN, which can be read from ~/.hermes/.env or ~/.git-credentials. Local diff reviews use plain git and need no API access at all.

When should I approve versus request changes on a PR?

Approve when there are no critical or warning-level issues. Request changes when any critical issue (security vulnerabilities, data loss, broken functionality) or warning exists. Use comment-only reviews for draft PRs or uncertain, non-blocking observations.