review-pr

Analyze pull requests and post structured GitHub PR reviews.

6|1|Updated Apr 26, 2025
One-click install
npx skills add https://github.com/edobry/minsky --skill review-pr-edobry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/edobry/minsky/tree/main/.claude/skills/review-pr
Command: npx skills add https://github.com/edobry/minsky --skill review-pr-edobry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR reviews often struggle to identify codebase-verified issues in large diffs and evolving specs. This Skill provides a structured, reproducible workflow that grounds findings in the codebase and the task specification.

Core Features & Use Cases

  • Gather PR context: fetch PR metadata, CI status, the diff, and the associated task spec to ensure alignment with requirements.
  • Identify the task and verify scope: extract task IDs from the PR title or branch name and retrieve the task spec for success criteria.
  • Diff analysis and coverage: read diffs, distribute the review workload for large PRs via parallel reviewer agents, and ensure full coverage of changes.
  • Post-verification review: synthesize findings into a GitHub PR review, marking blockers, non-blockers, and alignment with the task spec.

Quick Start

Provide the PR number or URL to trigger an automated, codebase-verified review and post a GitHub PR 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 GitHub PR reviews with codebase-verified findings?

To automate GitHub PR reviews, this Skill fetches PR metadata, CI status, and diffs in parallel, then grounds its analysis in the codebase and task spec to post structured findings directly to GitHub.

How does automated code review handle large pull request diffs?

For large pull request diffs, the automated review dispatches parallel reviewer agents to distribute the workload, ensuring full code coverage before synthesizing and posting the final GitHub review.

Can I verify a pull request against its original task spec?

Yes, you can verify a pull request against its task spec. The review process extracts the task ID from the PR title or branch name, retrieves the spec, and checks the diff for alignment with success criteria.

What is the best way to post structured PR reviews with blockers and non-blockers?

The best way to post structured PR reviews is to synthesize analyzed diff findings into a GitHub review, explicitly categorizing identified issues as blockers, non-blockers, or spec alignment deviations.

How do I gather CI status and changed files for a GitHub pull request?

To gather CI status and changed files for a GitHub pull request, provide the PR number or URL and the context will be fetched in parallel, ensuring efficient extraction of metadata for the review.