pr-check

Automate GitHub pull request readiness checks for branch state and metadata.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the commonly missed PR readiness checks to ensure a clean worktree, clear descriptions, and a properly squashed body before review.

Core Features & Use Cases

  • Verify branch state (not on main/master) and detect uncommitted changes.
  • Validate PR metadata including title quality, body quality, and the existence of a base branch, ensuring a smooth review process.
  • Integrate into typical development workflows to catch issues early and reduce back-and-forth during code review.

Quick Start

Run /pr-check to validate your current worktree and PR readiness before requesting a review.

Frequently Asked Questions about pr-check

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

FAQPage Schema
How do I check if my pull request is ready for code review?

To check if a pull request is ready for review, validate the Git branch state, ensure there are no uncommitted changes, and verify the PR title and body quality. Automating these readiness checks catches issues early and reduces back-and-forth during code review.

What is included in a GitHub PR readiness check?

A GitHub PR readiness check includes verifying you are not on main/master, detecting uncommitted changes, validating the base branch exists, and reviewing PR title and body quality. It also checks the draft status to ensure the pull request is ready for review.

How do I automate pull request validation for uncommitted Git changes?

You can automate pull request validation to detect uncommitted Git changes by running a readiness check before requesting review. This ensures a clean worktree, verifies the base branch, and validates PR metadata like title and body quality automatically.

Can I use an automated PR check for standard Git branching workflows?

Yes, you can use an automated PR check for standard Git branching workflows. It applies to software development processes using Git branches and feature work, verifying branch state and PR existence to ensure clean descriptions before review.

Why does my pull request fail a branch state validation check?

A pull request fails branch state validation if you are working directly on main/master, have uncommitted changes in your worktree, or lack a properly defined base branch. Readiness checks identify these issues to prevent broken reviews.