review-pr

Automate GitHub pull request reviews with the gh CLI.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/rokkay/dotfiles-macos --skill review-pr-rokkay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/rokkay/dotfiles-macos/tree/main/config/claude/skills/review-pr
Command: npx skills add https://github.com/rokkay/dotfiles-macos --skill review-pr-rokkay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams efficiently review and merge GitHub pull requests using the gh CLI, ensuring CI checks are green before merging.

Core Features & Use Cases

  • Fetch PR details, diffs, and CI status to inform decisions
  • Post review comments or request changes directly on the PR
  • Merge PRs with squash and tag a release when CI is green

Quick Start

Review a PR using the gh CLI to fetch details, review the changes, and merge if CI checks pass.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I automate a GitHub pull request review and check CI status?

Automate a GitHub pull request review by using the gh CLI to fetch PR details, diffs, and CI status. This process enforces a workflow that checks CI, posts feedback, and merges with squash when CI checks pass.

Can I merge a pull request with squash only when CI checks pass?

Yes, you can merge a pull request with squash conditionally. The workflow verifies that CI checks are green before merging the PR and tagging a release per the repository guidelines.

How do I post review comments and request changes on a GitHub PR via command line?

Post review comments and request changes on a GitHub PR by fetching the diff via the gh CLI. This allows you to review changes and post feedback or request modifications directly on the pull request.

Does this PR review workflow require any specific GitHub repository guidelines?

The PR review workflow enforces repository guidelines by tagging releases after merging. It integrates directly with the gh CLI to fetch details and ensure CI status is green before completing the merge.

What is the best way to verify CI status and tag a release after merging a GitHub PR?

The best way to verify CI status and tag a release is to use an automated gh CLI workflow. It fetches CI checks, enforces a green status before merging with squash, and tags a release according to repository guidelines.