github-code-review

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

5|2|Updated May 26, 2026
One-click install
npx skills add https://github.com/perasyudha/Nyxora --skill github-code-review-perasyudha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-code-review
Source: https://github.com/perasyudha/Nyxora/tree/main/packages/core/playbooks/github/github-code-review
Command: npx skills add https://github.com/perasyudha/Nyxora --skill github-code-review-perasyudha

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 git diffs, GitHub API calls, and structured feedback formatting, which is tedious and error-prone when done manually. ## Core Features & Use Cases - Local Pre-Push Review: Analyze staged or branch diffs with plain git, scanning for debug statements, secrets, conflict markers, and common code issues. - Pull Request Review: Fetch PR details, check out PR branches locally, run tests, and submit formal reviews (approve, request changes, comment) with inline comments via gh CLI or curl. - Structured Feedback: Produce severity-tiered review summaries (Critical, Warnings, Suggestions, Looks Good) using a consistent output template. - Use Case: A teammate asks you to review PR #123. The skill checks out the PR, runs the test suite, applies a review checklist covering correctness, security, and testing, then posts inline comments and a summary verdict directly to GitHub. ## Quick Start Review pull request number 123 in this repository and post your findings as inline comments and a summary 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. Submit feedback using gh pr review or by posting to the GitHub reviews API endpoint with curl.

How to add inline comments to a GitHub PR via API?

Post to the /repos/{owner}/{repo}/pulls/{number}/comments endpoint with the file path, line number, commit SHA, and comment body. You can also batch multiple inline comments into a single atomic review via the /reviews endpoint.

Can I review code without the gh CLI installed?

Yes, all PR interactions work with plain git plus curl against the GitHub REST API using a GITHUB_TOKEN. Local pre-push reviews only need git diff commands and require no API access at all.

What should a code review checklist include?

A thorough checklist covers correctness, security issues like hardcoded secrets and injection risks, code quality, test coverage, performance concerns, and documentation. The skill applies these categories systematically to every changed file.

When should I request changes versus approve a pull request?

Approve when only minor suggestions exist, request changes when any critical or warning-level issue is found, and use comment-only reviews for draft PRs or uncertain findings. This maps to the APPROVE, REQUEST_CHANGES, and COMMENT review events.