gh-pr-review

Automate GitHub pull request reviews and merges via the gh CLI with JSON outputs.

1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/squirrel289/pax --skill gh-pr-review-squirrel289
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-pr-review
Source: https://github.com/squirrel289/pax/tree/main/skills/tools/gh-pr-review
Command: npx skills add https://github.com/squirrel289/pax --skill gh-pr-review-squirrel289

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines GitHub pull request review and management by enabling concise CLI-driven interactions, comments, and merges.

Core Features & Use Cases

  • View PR details: quickly fetch title, state, author, mergeability, and status checks.
  • Review management: list, reply to, and resolve review threads to keep PR discussions organized.
  • Merge readiness and actions: assess merge readiness and perform merges or updates safely via CLI.

Quick Start

View a PR, read reviews, and reply to comments using the gh-pr-review CLI to manage PRs end-to-end.

Frequently Asked Questions about gh-pr-review

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

FAQPage Schema
How do I manage GitHub pull request reviews from the command line?

You can manage GitHub pull request reviews from the command line by using this skill to fetch PR details, list reviews, reply to comments, resolve threads, and perform merges via the GitHub CLI.

Can I check PR merge readiness and status checks via CLI?

Yes, you can check PR merge readiness via CLI by fetching the pull request state, mergeability status, and check results to assess if a branch is safe to merge.

How do I automate replying to and resolving PR review threads?

Automating PR review thread management involves using CLI commands to list existing review comments, reply directly to threads, and mark them as resolved to keep discussions organized.

Do I need the GitHub CLI installed to automate pull request workflows?

Yes, you need the GitHub CLI installed and available in your environment, as this skill relies on it to execute commands for viewing, reviewing, and merging pull requests.

What is the best way to handle multiple pull requests with standardized JSON outputs?

The best way to handle multiple PRs is using a CLI-based workflow that standardizes outputs into JSON format, ensuring consistent data parsing and error handling across batch operations.

Are there limitations when merging pull requests via command line automation?

Limitations include dependency on GitHub CLI availability and potential merge failures if status checks fail or merge conflicts exist, requiring manual resolution before merging.