pr-split

Split Git feature branches into stacked PRs with 500-1000 line targets.

1|1|Updated Jun 11, 2024
One-click install
npx skills add https://github.com/ag-grid/ag-shared --skill pr-split
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-split
Source: https://github.com/ag-grid/ag-shared/tree/main/prompts/skills/pr-split
Command: npx skills add https://github.com/ag-grid/ag-shared --skill pr-split

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Split a large feature branch into a sequence of smaller, review-friendly PRs that are easier to review and reason about.

Core Features & Use Cases

  • Each PR addresses a single concern and preserves a coherent narrative across the stack.
  • PRs are designed to pass all quality checks and include clear, descriptive commit messages.
  • The workflow supports deterministic planning, staging changes from a temporary branch, and rebase-friendly histories.

Quick Start

Split the current feature branch into a series of stacked PRs that each address a single concern and maintain a coherent narrative.

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 Git feature branch into smaller pull requests?

To split a large Git feature branch into smaller pull requests, this Skill automatically transforms the branch into a sequence of review-friendly PRs. Each PR addresses a single concern while preserving a coherent narrative across the changes.

What is the best way to automate code review for massive feature branches?

The best way to automate code review for massive feature branches is deterministic planning that enforces 500-1000 line PR targets. This approach uses clear, prefix-based commit messages to support traceability and ensure each PR passes all quality checks.

Can I stage changes from a temporary branch to create stacked PRs?

Yes, you can stage changes from a temporary branch to create stacked PRs. The workflow supports deterministic planning and rebase-friendly histories, ensuring the split pull requests maintain a coherent narrative flow across the stack.

Does this branch management workflow require specific dependencies to split pull requests?

No specific dependencies are required to split pull requests with this branch management workflow. The automation operates directly on Git feature branches to enforce 500-1000 line PR targets and generate clear, prefix-based commit messages.

Why should I split a feature branch before requesting code review?

You should split a feature branch before code review because smaller PRs are easier to review and reason about. This automation ensures each PR addresses a single concern, maintains a coherent narrative, and passes all quality checks.

What are the limitations of automated branch splitting for code review?

A limitation of automated branch splitting is that it applies specifically to Git feature branches to streamline code review. While it enforces 500-1000 line PR targets and prefix-based commit messages, complex branch histories may require manual rebase-friendly adjustments.