gh-pr-review

Manage GitHub PR pending reviews and diff-line comments via gh-review.

1|Updated Jun 1, 2025
One-click install
npx skills add https://github.com/rcdailey/dotfiles --skill gh-pr-review-rcdailey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-pr-review
Source: https://github.com/rcdailey/dotfiles/tree/main/home/dot_config/opencode/exact_skills/gh-pr-review
Command: npx skills add https://github.com/rcdailey/dotfiles --skill gh-pr-review-rcdailey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines code review workflows by guiding inline and body comments and managing pending reviews through the gh-review tool.

Core Features & Use Cases

  • Enforces a safe review workflow: comments go through a pending review, not directly submitted.
  • Manages PR review state: start, view, and delete pending reviews and append comments on specific diff lines.
  • Supports structured review etiquette and automated verification prompts to improve review quality.

Quick Start

Start a pending PR review for a repository using gh-review

Frequently Asked Questions about gh-pr-review

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

FAQPage Schema
How do I add inline comments to a GitHub PR review without submitting them directly?

Pending PR reviews act as a temporary holding state for your comments before final submission. This Skill uses gh-review primitives to start, view, and delete pending reviews, enforcing a workflow where comments are collected safely rather than submitted directly to the PR.

How do I start and manage a pending GitHub PR review?

You manage a pending GitHub PR review by using gh-review primitives to start, view, and delete review states. This Skill coordinates the workflow by allowing you to append comments on specific diff lines and collect any failures for manual posting.

Can I use this to coordinate code review etiquette for my team?

Yes, this coordinates code review etiquette by enforcing structured workflows and automated verification prompts. It guides inline and body comments through a pending review state, ensuring teams collect feedback safely without directly submitting comments to the GitHub PR.

Why does my GitHub PR review workflow require a pending review state?

Your GitHub PR review workflow requires a pending review state to enforce safe submission rules. The Skill prevents direct review submissions, ensuring comments and collected failures are verified through gh-review primitives before you manually post them to the code diff.

What are the limitations of automating PR reviews with gh-review primitives?

The main limitation is that this Skill never submits reviews directly and only manages pending review states. You must manually post any collected failures and comments to GitHub, meaning the final review submission remains a required manual action outside the automated workflow.