split-pr

Split GitHub pull requests into smaller ones by CODEOWNERS reviewer groups.

Updated May 23, 2026

Search Tags:#pull request #dependency management #github #monorepo #repository maintenance #codeowners #review workflow

Ready to run

npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill split-pr-yo-steven

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: split-pr
Source: https://github.com/yo-steven/skills-exploration-20260522/tree/main/skills/Megatron-Core/split-pr
Command: npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill split-pr-yo-steven

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Split a large GitHub pull request into smaller PRs so that each new PR requires fewer CODEOWNERS reviewer groups, reducing review burden and speeding up approval.

Core Features & Use Cases

CODEOWNERS-aware file grouping: Analyze changed files and map them to CODEOWNERS owner groups to understand which reviewers each part of the PR will involve.
Optimization to minimize reviewer groups: Propose a split that clusters files by their required reviewer groups, using the largest cluster first and grouping the rest to keep reviewer sets small.
Dependency-aware sequencing: Explicitly handle cases where one split PR must be merged before another due to renames or symbol dependencies, ensuring each PR can be merged cleanly to main.

Quick Start

Use the split-pr skill to split PR number you specify by analyzing NVIDIA/Megatron-LM CODEOWNERS, proposing an optimized multi-PR plan, and then creating draft PRs on your fork after you approve the proposed split.

Frequently Asked Questions about split-pr

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

FAQPage Schema

How do I split a large pull request into smaller ones for CODEOWNERS?▼

To split a pull request, you analyze changed files and map them to CODEOWNERS reviewer groups. The tool proposes an optimized multi-PR plan that clusters files by their required reviewer groups, keeping reviewer sets small to speed up approval.

What is the best way to handle a monorepo pull request that requires too many reviewers?▼

The best way to handle a monorepo pull request with too many reviewers is to split it into multiple smaller PRs. Grouping changed files according to CODEOWNERS reviewer groups minimizes the distinct reviewers required for each individual PR.

How does dependency-aware sequencing work when splitting a GitHub pull request?▼

Dependency-aware sequencing ensures each split PR can merge cleanly to main. It explicitly handles cases where one split PR must be merged before another due to renames or symbol dependencies, creating a sequenced and mergeable split plan.

Can I automatically create draft PRs on my fork after splitting a pull request?▼

Yes, you can automatically create draft PRs on your fork. After analyzing the PR diff, parsing CODEOWNERS patterns, and approving the proposed optimized split plan, the tool handles draft PR creation directly on your repository fork.

Why does my monorepo pull request pull in too many distinct CODEOWNERS reviewer groups?▼

A monorepo pull request pulls in too many distinct CODEOWNERS reviewer groups when a single PR touches many directories. Splitting the PR clusters files by their required reviewer groups to reduce the overall review burden.