Agent skill · NVIDIA
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
What it needs
About 3k tokens when loaded.
What this skill does
Split PR by CODEOWNERS Groups Split a large pull request into multiple smaller PRs, where each PR touches the fewest possible CODEOWNERS reviewer groups. The goal is to reduce review burden: a PR that only touches megatron/core/ needs only the core reviewers, while a PR that also touches examples/, tools/, and megatron/training/ pulls in many additional groups. Answer-First Constraints For split-planning questions, lead with these constraints before the full workflow: Minimize CODEOWNERS reviewer groups per PR, but each resulting PR must still be independently mergeable and reviewable. Tests travel with the production code they validate; do not split tests into a separate PR just to reduce reviewer groups. If PR B depends on symbols renamed in PR A, call out the dependency and put backward-compatible aliases, re-exports, or shims in PR A when needed. Wait for user approval before execution. Execution creates draft PRs from the right base, applies file-scoped diffs with git diff upstream/main..<source-branch> -- <paths> git apply, pushes to the user's fork, and never pushes directly to upstream. Workflow 1. Analyze the PR 1. Fetch the PR details: gh pr view <number> --repo NVIDIA/Megatron-LM --json title,body,headRefName,author and gh pr diff <number> --repo NVIDIA/Megatron-LM --stat. Also determine the current GitHub user with gh api user --jq .login. 2. Parse .github/CODEOWNERS to build a mapping from file path patterns to owner groups. 3. For each changed file in the PR, determine which CODEOWNERS groups would be required to review it. 4. Build a summary table grouped by CODEOWNERS group, showing which files pull in which groups. 5. Count the total number of distinct reviewer groups the PR currently requires. 2. Propose a split that minimizes reviewer groups per PR The primary optimization goal: minimize the number of CODEOWNERS reviewer groups required for each resulting PR. Strategy: 1. Cluster files by their CODEOWNERS groups. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills NVIDIA/mcore-split-pr