review-pr

Review GitHub pull requests and post structured maintainer verdict comments.

2|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/rafrusth/job_application --skill review-pr-rafrusth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/rafrusth/job_application/tree/main/job-web/vendor/livewire/livewire/.claude/skills/review-pr
Command: npx skills add https://github.com/rafrusth/job_application --skill review-pr-rafrusth

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, grep, phpunit.

What problem does it solve?

It streamlines reviewing pull requests by enforcing maintainer-grade checks, applying fixups when safe, running targeted tests, and posting a clear verdict comment so maintainers can merge or close quickly.

Core Features & Use Cases

  • Maintainer-style PR triage: Selects the latest open PR (or a specified PR number), checks for prior Claude reviews, and classifies the PR as Bug fix, Feature, Refactor, Docs, or Mixed.
  • Independent validation: Verifies the contributor’s framing by reading the actual diff to confirm the root cause and whether tests truly isolate it.
  • Safe fix-and-merge workflow: Checks out the PR, merges main into the branch, applies practical improvements (style, missing tests, docs, registration), pushes fixes, and posts a structured verdict comment.
  • Targeted testing and CI checks: Runs only relevant tests for touched files (or newly written tests) and inspects PR check status to avoid unnecessary test-suite runs.

Quick Start

Use the review-pr skill to review the latest open pull request and post a structured maintainer verdict comment after checking the diff, applying any fixups you can, and running only the relevant tests.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I review a GitHub pull request like a maintainer?

To review a GitHub pull request like a maintainer, you select the target PR, verify if it was already reviewed, fetch PR metadata and diff context, and check out the branch with main merged for accurate analysis before running relevant tests.

Can I run targeted tests on a PR branch instead of the full test suite?

Yes, you can run targeted tests on a PR branch by checking out the branch, merging main into it, and running only relevant PHPUnit tests for touched files or newly written tests to avoid unnecessary full test-suite runs.

How does automated pull request classification work for code changes?

Automated pull request classification works by reading the actual diff to independently verify the contributor's framing, categorizing the code changes as a Bug fix, Feature, Refactor, Docs, or Mixed contribution.

Do I need GitHub CLI to triage open pull requests?

Yes, you need GitHub CLI and related git operations to triage open pull requests, as the workflow requires fetching PR metadata, checking out branches, inspecting PR check status, and enforcing mandatory step ordering.

What is a safe fix-and-merge workflow for pull requests?

A safe fix-and-merge workflow for pull requests involves checking out the PR, merging main into the branch, applying practical improvements like style fixes and missing tests, pushing fixes, and posting a structured verdict comment.

What are the limitations of automated PR review for Livewire-style contributions?

Automated PR review for Livewire-style contributions is limited to specific scenarios covering bug fixes, features, refactors, and documentation changes with security, style, test, and CI validation, enforcing a strict mandatory step ordering.