split-pr

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.

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.

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.

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.

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.