github-code-review

Review GitHub code changes and pull requests with inline feedback.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/TitoPrausee/nexus-toti --skill github-code-review-titoprausee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-code-review
Source: https://github.com/TitoPrausee/nexus-toti/tree/main/data/skills/github/github-code-review
Command: npx skills add https://github.com/TitoPrausee/nexus-toti --skill github-code-review-titoprausee

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you review code changes efficiently before push or on GitHub pull requests, turning raw diffs into structured feedback with clear severity levels.

Core Features & Use Cases

  • Local pre-push review: Inspect staged changes or branch diffs for correctness, security issues, code quality problems, and missing tests.
  • GitHub PR review: Gather PR details, review changed files, and leave general or inline comments with gh CLI or GitHub REST API.
  • Structured decision-making: Produce consistent outcomes such as approve, request changes, or comment, with a summary organized by critical issues, warnings, suggestions, and positives.

Quick Start

Ask the skill to review the current branch or a specific pull request and return a structured code review with severity-ranked findings.

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 with inline comments?

You can review a GitHub pull request by gathering changed files and PR metadata, then submitting formal review decisions and inline comments via gh CLI or GitHub REST API, producing structured feedback organized by severity.

Can I review local git diffs before pushing to a remote branch?

Yes, you can inspect staged changes or local branch diffs before pushing to identify correctness, security issues, and missing tests, generating structured pre-push feedback with severity-ranked findings and actionable suggestions.

Does this code review approach work with both gh CLI and curl?

Yes, it supports fetching file diffs, PR metadata, and submitting review comments using either gh CLI or git plus GitHub REST API via curl, requiring either tool configured for repository access to return formal review decisions.

What is the best way to structure pull request review feedback?

The best way to structure pull request review feedback is organizing findings into critical issues, warnings, suggestions, and positives, yielding consistent approval, request changes, or comment decisions for the PR author.

How does automated code review handle approval decisions on GitHub?

Automated code review handles approval decisions by analyzing git diffs for correctness and security, then submitting a formal GitHub review with an approve, request changes, or comment outcome accompanied by inline comments and a summary.

What are the limitations of using REST API for PR review comments?

Using GitHub REST API via curl for PR review comments requires proper authentication and manual mapping of inline comments to diff positions, lacking native conversation threading resolution but enabling automated formal review submissions.