pr-review

Automate pre-merge quality checks for pull requests and generate a consolidated report.

29|4|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/matsen/bipartite --skill pr-review-matsen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/matsen/bipartite/tree/main/skills/pr-review
Command: npx skills add https://github.com/matsen/bipartite --skill pr-review-matsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates a comprehensive pre-merge quality checklist for pull requests to catch issues early and streamline reviews.

Core Features & Use Cases

  • Project-type detection to apply relevant checks (linting, tests, security scans).
  • Selective review of changed files to focus feedback on modified code.
  • Agent-based validation and automated report generation for PRs.
  • Generates a consolidated pre-merge report suitable for CI dashboards and reviewer notifications.

Quick Start

Run the pr-review workflow on the current branch to execute automated pre-merge quality checks and generate a summary report.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I automate pre-merge quality checks for pull requests?

To automate pre-merge quality checks for pull requests, you can use a workflow that identifies the project type, validates changed files, runs agent reviews, and generates a consolidated report. This catches issues early and streamlines reviews.

What is the best way to run automated code reviews on modified files?

The best way to run automated code reviews on modified files is using selective review that focuses feedback on changed code. This approach applies relevant checks like linting and testing specifically to the modified files in the pull request.

How does project type detection work for pull request automation?

Project type detection for pull request automation works by identifying the repository type to apply relevant checks. This ensures appropriate linting, tests, and security scans are executed based on the specific project framework and structure.

Can I generate a consolidated pre-merge report for CI dashboards?

Yes, you can generate a consolidated pre-merge report for CI dashboards. The automated workflow produces a summary report suitable for reviewer notifications and dashboard integration after validating all changed files.

Do I need code hosting platform integration to review pull requests?

Yes, code hosting platform integration is required to review pull requests. The automation needs access to diff data and code hosting platforms to identify changed files and perform agent-based validation across multiple steps.