pr-split

Assess pull request size and propose ordered split plans.

5|3|Updated Jun 18, 2024

Search Tags:#git #workflow #split #pr #atomicity #code-review #pull-request

Ready to run

npx skills add https://github.com/Unique-AG/ai --skill pr-split-unique-ag

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-split
Source: https://github.com/Unique-AG/ai/tree/main/.claude/skills/pr-split
Command: npx skills add https://github.com/Unique-AG/ai --skill pr-split-unique-ag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Oversized PRs slow reviews and increase risk. This skill helps teams assess PR size and outline a plan to split large changes into focused, reviewable PRs.

Core Features & Use Cases

Size assessment: calculates files changed, lines added, and potential logical concerns to determine if a PR is too large.
Threshold and atomicity checks: determines if changes require splitting or can be submitted as-is.
Split planning: proposes an ordered sequence of smaller PRs and guidance on branch strategy.
Documentation: helps document unsplittable PRs when necessary.

Quick Start

Paste your PR stats or diff and I will guide you through sizing, splitting, and sequencing the PRs.

Frequently Asked Questions about pr-split

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

FAQPage Schema

How do I split a large pull request into smaller, focused chunks?▼

This Skill splits oversized pull requests by evaluating diff stats to identify distinct concerns, ordering them into an incremental sequence of smaller, reviewable PRs with branch strategy guidance.

When should I split a pull request before code review?▼

You should split a pull request when threshold and atomicity checks determine the changes are too large or contain multiple distinct concerns, slowing reviews and increasing risk. The Skill automates this sizing assessment.

What is the best way to enforce atomicity in a git workflow?▼

Enforce atomicity in a git workflow by evaluating distinct concerns within changes and sequencing them incrementally. This Skill performs atomicity checks and proposes a split plan to keep PRs focused.

How do I sequence incremental PRs for an oversized branch?▼

Sequence incremental PRs for an oversized branch by identifying distinct concerns and ordering them logically. This Skill generates the ordered split plan and provides branch strategy guidance for the sequence.

What should I do if a pull request cannot be split for review?▼

If a pull request cannot be split, you should document the unsplittable changes clearly. This Skill helps document oversized PRs when splitting is not feasible, ensuring reviewers understand the context.