gh:pr-approve

Evaluate GitHub PR diffs and comments to approve, request changes, or log follow-ups.

Updated May 31, 2025
One-click install
npx skills add https://github.com/dEitY719/dotfiles --skill gh-pr-approve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh:pr-approve
Source: https://github.com/dEitY719/dotfiles/tree/main/claude/skills/gh-pr-approve
Command: npx skills add https://github.com/dEitY719/dotfiles --skill gh-pr-approve

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Review a GitHub PR, approve it when clean, request changes for blockers, or file follow-up issues for non-blocking concerns. Use for /gh-pr-approve, /gh:pr-approve, "approve PR 99", "#99 리뷰 승인", or "re-review requested". Self-authored PRs cannot be approved; they use analysis-only, comment-only, or admin-merge paths.

Core Features & Use Cases

  • Pre-flight gate — checks PR state, draft status, blockers, and basic CI status, stopping the flow early on blockers.
  • Fetches review material — diffs, commits, and the three comment endpoints (inline / issues / reviews) to gather feedback comprehensively.
  • Classification & action — evaluates findings as BLOCKER, FOLLOW-UP, or PRAISE and submits the corresponding GitHub action (approve, request changes, or log follow-ups).
  • Re-review support — in case prior ME reviews exist, re-checks all concerns to ensure they’re addressed or properly tracked.
  • External reporting — generates a concise status summary and guidance for external reviewers or automation pipelines.

Quick Start

Review PRs with the gh-pr-approve skill by supplying the target PR number and remote, for example gh-pr-approve 99 origin.

Frequently Asked Questions about gh:pr-approve

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

FAQPage Schema
How do I automate GitHub PR reviews to approve or request changes?

Automate GitHub PR reviews by evaluating PR state, diffs, and feedback endpoints to determine whether to approve, request changes, or log follow-ups. It classifies findings as BLOCKER, FOLLOW-UP, or PRAISE and outputs a structured review plan.

What is the best way to handle GitHub PR blockers and follow-ups automatically?

Handle PR blockers and follow-ups by fetching diffs, commits, and comments, then classifying findings to submit corresponding GitHub actions. Blockers trigger change requests, while non-blocking concerns are logged as follow-up issues.

Can I use automated PR approval on self-authored GitHub pull requests?

Self-authored PRs cannot be approved automatically; they use analysis-only, comment-only, or admin-merge paths. This safety rule prevents authors from approving their own code through automation.

Does automated PR review support re-reviewing when prior comments exist?

Re-review support checks all prior concerns when previous reviews exist to ensure they are addressed or properly tracked. This handles updated pull requests by re-evaluating feedback endpoints.

What are the limitations of automating PR approvals across forks and remotes?

Automating PR approvals across forks and remotes enforces safety rules with a pre-flight gate checking draft status, blockers, and CI status, stopping the flow early on blockers. External reporting generates concise status summaries.