pr

Generate reviewer-first PR descriptions and sizing guidance for software changes.

21|6|Updated Dec 10, 2025
One-click install
npx skills add https://github.com/mintuz/claude-plugins --skill pr-mintuz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/mintuz/claude-plugins/tree/main/plugins/core/skills/pr
Command: npx skills add https://github.com/mintuz/claude-plugins --skill pr-mintuz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines writing clear, reviewer-friendly PR descriptions and provides sizing/splitting guidance with practical templates and gh CLI workflows.

Core Features & Use Cases

  • Templates for PR descriptions: Small, medium, and large PR formats that help structure changes and testing.
  • PR sizing guidance: Tools to decide when to split large changes into multiple PRs.
  • GitHub CLI workflows: Step-by-step gh pr commands to create and manage PRs efficiently.

Quick Start

Use the PR templates to draft a description and create a PR with gh pr create, following the recommended templates.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I write a pull request description that is easy to review?

PR sizing guidance helps decide when to split large pull requests by evaluating the scope of changes. It provides criteria to break down large modifications into multiple smaller PRs, ensuring changes remain manageable and fast to review.

What's the best way to create a pull request using gh CLI?

The best way to create a pull request using gh CLI is to follow step-by-step gh pr workflows. This involves selecting a fitting PR template, drafting the description, and executing the gh pr create command to manage the submission efficiently.

Does this PR workflow support both small bug fixes and large feature branches?

Yes, this PR workflow supports both small bug fixes and large feature branches by offering distinct templates for small, medium, and large PRs. It guides template selection and scoping based on the specific size and complexity of the code changes.

When should I split a large pull request into multiple smaller ones?

You should split a large pull request when the scope exceeds manageable review limits. The provided sizing guidance evaluates change volume and complexity, recommending separation into multiple sequential PRs to maintain code review quality and speed.