review-pr

Automate maintainer-style GitHub PR reviews with structured verdict comments.

31.8k|1.4k|Updated Nov 28, 2019
One-click install
npx skills add https://github.com/alpinejs/alpine --skill review-pr-alpinejs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/alpinejs/alpine/tree/main/.claude/skills/review-pr
Command: npx skills add https://github.com/alpinejs/alpine --skill review-pr-alpinejs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainer teams spend time on repetitive PR reviews and risk inconsistent verdicts. This Skill automates the end-to-end PR review workflow, ensuring consistency and speed.

Core Features & Use Cases

  • Automates the full PR review lifecycle: checkout, data fetch, analysis, and verdict posting.
  • Enforces a strict, step-by-step review process to maintain consistency across PRs.
  • Works with open PRs on GitHub, selecting the latest if no PR number is provided, and posts structured feedback to help maintainers.

Quick Start

Provide a PR number to start the review, or omit it to pick the latest open PR, and let the bot perform the maintainer-style review.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I automate maintainer-style PR reviews on GitHub?

To automate GitHub PR reviews, this Skill executes an end-to-end workflow that fetches open PRs, merges the main branch, evaluates changes, and posts a structured verdict comment automatically.

What is the process for automated PR review on open GitHub pull requests?

Automated PR review follows a strict, step-by-step sequence: marking the PR checked, fetching data, merging the main branch, evaluating changes, and posting a structured verdict comment using CLI commands.

Do I need to provide a PR number to start the GitHub review automation?

You do not need to provide a PR number to start GitHub review automation; if omitted, the Skill automatically targets the latest open PR and applies the strict review flow.

How does this automation ensure consistency and prevent duplicate PR reviews?

PR review consistency and safety are ensured by enforcing a fixed sequence of CLI actions and guarding against re-review, preventing duplicate or inconsistent verdicts across different pull requests.

Can I use this automated review workflow for any open GitHub PR?

Yes, you can use this automated review workflow for any open GitHub PR. It selects the latest open PR by default or targets a specific PR when you provide its number.