split-pr

To split a pull request and reduce CODEOWNERS reviewer groups, the Skill parses your repository's .github/CODEOWNERS file and the PR diff. It clusters changed files by the reviewer groups they trigger, proposing an ordered split that minimizes the review scope for each resulting PR.

The best way to break down a large GitHub PR touching multiple owned paths is clustering files by their CODEOWNERS groups. The Skill selects a largest first PR and structures remaining PRs to minimize additional reviewer groups, ensuring each resulting PR requires fewer distinct reviewers to merge.

When splitting a git diff into multiple draft PRs, the Skill ensures dependency-aware execution. It accounts for branch ordering when later PRs depend on symbols or refactors introduced earlier, keeping all resulting PRs independently mergeable without breaking your codebase.

Yes, you can create draft PRs on your fork after splitting a pull request. The Skill generates new branches from the correct base and executes draft PR creation on the user's fork, strictly waiting for your explicit approval before creating any pull requests and avoiding force-pushes.

Splitting a pull request by CODEOWNERS groups keeps resulting branches independently mergeable. The Skill applies dependency-aware execution to ensure follow-on PRs account for ordering when later PRs depend on symbols or refactors introduced earlier, preventing merge conflicts and build failures.