github-code-review

Review pull requests and post inline comments on GitHub using gh or curl.

33|1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/infinition/LaRuche --skill github-code-review-infinition
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-code-review
Source: https://github.com/infinition/LaRuche/tree/main/laruche/skills/github-code-review
Command: npx skills add https://github.com/infinition/LaRuche --skill github-code-review-infinition

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Reviewing code changes and leaving structured feedback on GitHub pull requests requires juggling git commands, the GitHub API, and consistent review formatting, which is slow and error-prone when done manually. ## Core Features & Use Cases - Local Pre-Push Review: Scan local diffs with git for debug statements, hardcoded credentials, and merge conflict markers before pushing. - Pull Request Review: Gather PR context, check out branches, run tests, and submit formal reviews (approve, request changes, or comment) via the gh CLI or curl with a GitHub token. - Structured Inline Feedback: Post atomic reviews with severity-tagged inline comments (critical, warning, suggestion) using a consistent output template. - Use Case: A teammate opens a PR touching authentication code. Check out the branch, diff against main, run the test suite, then submit a single atomic review flagging a SQL injection at a specific line and approving the rest. ## Quick Start Review pull request number 42 in this repository and leave inline comments on any security 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?▼

Use gh pr view and gh pr diff to inspect the PR, gh pr checkout to test it locally, then gh pr review with --approve, --request-changes, or --comment to submit a formal verdict. Inline comments are posted via gh api against the pulls comments endpoint.

How do I leave an inline comment on a specific line of a pull request?▼

Fetch the PR head commit SHA, then POST to the pulls comments endpoint with the file path, line number in the new file, side RIGHT, and the commit_id. For deleted lines, use side LEFT instead.

Can I review GitHub PRs without the gh CLI installed?▼

Yes, curl with a GITHUB_TOKEN works as a fallback for every operation, including fetching PR metadata, listing changed files, posting comments, and submitting atomic reviews with multiple inline comments in one API call.

How do I check my code for issues before pushing to GitHub?▼

Run git diff main...HEAD and grep the output for debug statements, credential patterns like passwords or API keys, and merge conflict markers. Then read the flagged files for full context before deciding on fixes.

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

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 drafts or informational observations.