gh-pr-review

Create pending GitHub PR reviews with line comments via gh CLI.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/nilpath/nilpath-marketplace --skill gh-pr-review-nilpath
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-pr-review
Source: https://github.com/nilpath/nilpath-marketplace/tree/main/plugins/claude-code-tools/skills/gh-pr-review
Command: npx skills add https://github.com/nilpath/nilpath-marketplace --skill gh-pr-review-nilpath

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, git, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Automates GitHub PR reviews by creating pending reviews with line comments and submitting them via the gh CLI.

Core Features & Use Cases

  • Create pending reviews with inline line comments across files.
  • Submit reviews as APPROVE, REQUEST_CHANGES, or COMMENT, or keep as PENDING for later submission.
  • Read PR context and diff to attach targeted feedback during code reviews.

Quick Start

Pipe a JSON payload into the create-review script to start a pending PR review with line comments.

Frequently Asked Questions about gh-pr-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub PR reviews with line comments via the CLI?

Automate GitHub PR reviews by piping a JSON payload into the create-review script to start a pending review with inline line comments. It reads PR context and diffs to attach targeted feedback across changed files using the gh CLI.

Can I submit a PR review as APPROVE, REQUEST_CHANGES, or COMMENT using gh?

Yes, you can submit PR reviews as APPROVE, REQUEST_CHANGES, or COMMENT directly through the gh CLI. Alternatively, you can keep the review as PENDING to submit it later after drafting line comments.

Do I need jq and git to create pending reviews with inline comments?

Yes, you need jq for processing JSON payloads and a Git repository with a configured remote. The tool also requires gh authentication to read PR context and submit targeted feedback across changed files.

What's the best way to attach targeted feedback to specific files in a PR?

Attach targeted feedback by reading the PR context and diff to identify changed files, then drafting precise line comments within a pending review. This approach ensures your feedback maps directly to specific code lines before submission.

Why does my automated PR review fail to apply line comments across files?

Automated PR reviews fail if gh authentication is missing, jq cannot parse the JSON payload, or the local Git repository lacks a properly configured remote. Ensure all dependencies are installed and the repository is correctly linked.