AI Plugin Index
mcore-split-pr
Skill by NVIDIA · updated · ★ 3.7k
Splits a large pull request into smaller PRs so each one needs fewer CODEOWNERS reviewer groups. It is written for contributors to NVIDIA's Megatron-LM repository. mcore-split-pr is published by NVIDIA on GitHub.
Install mcore-split-pr
Built from the published package, never by AIgit clone --depth 1 https://github.com/NVIDIA/skills /tmp/skills && mkdir -p ~/.claude/skills && cp -r /tmp/skills/skills/mcore-split-pr ~/.claude/skills/mcore-split-prRun in your terminal. Claude Code loads skills from ~/.claude/skills automatically.
git clone --depth 1 https://github.com/NVIDIA/skills /tmp/skills && mkdir -p ~/.gemini/antigravity-cli/skills && cp -r /tmp/skills/skills/mcore-split-pr ~/.gemini/antigravity-cli/skills/mcore-split-prAntigravity CLI loads skills from ~/.gemini/antigravity-cli/skills, or .agents/skills for one project.
Skills can run scripts on your machine. Some need an API key: check the README.
Last commit in the past day
Apache-2.0: permissive, fine for commercial use
Clear description, installs from GitHub, 3,716 stars, original repository
No risky patterns in the files we checked
About mcore-split-pr
This agent skill takes a large pull request in NVIDIA/Megatron-LM and proposes a split into smaller PRs. It parses the repository's CODEOWNERS file, groups changed files by the reviewer groups they require, and aims to minimize the groups each new PR needs. Each proposed PR is shown as a table with its files, required groups and dependencies.
The skill only executes the split after the user approves the plan. It then creates each new branch from the right base, applies file-scoped diffs, pushes to the user's fork and opens the PRs as drafts. It never pushes directly to upstream. It is aimed at contributors to the Megatron-LM project who need to reduce review burden on large changes.
Written from the project's SKILL.md and checked against it.
What mcore-split-pr can do
- Analyze PRFetches PR details and diff stats, then maps each changed file to its CODEOWNERS groups.
- Propose splitClusters files by reviewer groups and proposes smaller PRs with their dependencies.
- Execute splitCreates branches, applies file-scoped diffs, pushes to the user's fork and opens draft PRs.
- Dependency handlingFlags when a PR depends on renamed symbols and suggests backward-compatible shims in the first PR.
What you need
- GitHub CLI (gh)
- git
- A fork of NVIDIA/Megatron-LM
- Approval of the proposed split before execution
Weekly newsletter
Like mcore-split-pr? Get the best new skills every week
The best new tools, security warnings before you install something risky, and one practical tip. Free, three minute read.
Try asking
- Split PR 1234 to reduce the number of CODEOWNERS reviewer groups.
- Show which CODEOWNERS groups each file in this PR pulls in.
- Break up this large Megatron-LM PR into smaller draft PRs.
Good to know
- Waits for user approval before executing any split.
- Never pushes directly to upstream; pushes go to the user's fork.
- Asks the user before force-pushing a narrowed original PR.
- Tests are kept with the production code they validate, not split out.
Security check
ANo download-and-run commands, hidden instructions or signs of sending keys out were found.
Checked automatically: skills/mcore-split-pr/SKILL.md. This looks for known risky patterns and is not a full audit. How grades work
Inside the skill
-
BENCHMARK.md3 KB -
SKILL.md4 KB -
evals/evals.json3 B -
skill-card.md2 KB -
skill.oms.sig4 KB
Alternatives to mcore-split-pr
All alternatives →
7-stage super workflow for GitHub repo audit, cleanup, PR review, and competitor analysis
Build Gradio web UIs and demos in Python. Use when creating, modifying, debugging, or answering questions about Gradio and its capabilties, components, event listeners, or layouts.
Writes the launch for an app clone: the landing page built on the positioning angle, pricing set against the original's public pricing and its users' complaints, and the App Store and Google Play listing linted against the stores' limits and copycat rules. Use when the user says "landing page", "pricing", "how much should I charge", "App Store listing", "store screenshots", "launch plan", "Product Hunt", or after /replica-brand.
Guides building end-to-end test suites with Playwright and Cypress. It is for developers who write E2E tests, debug flaky tests, or set testing standards.
Adds a self-hosted "Stargazers over time" chart to a GitHub repo's README. It generates a static SVG and refreshes it weekly with a GitHub Action. Useful when a third-party star chart shows "Requires authentication".
Creates production-ready FastAPI project structures with async patterns, dependency injection, and error handling. It is for developers starting new FastAPI applications or backend API projects.
mcore-split-pr: common questions
Does this skill push changes to the NVIDIA repository?
No. The source says it never pushes directly to upstream and pushes new branches to the user's fork instead.
What happens if a file touches two reviewer groups?
The skill asks the user which PR the file should go in.
Are the new PRs opened as drafts?
Yes. The source says each new PR is created as a draft, per the repo contributing guidelines.
How do I install mcore-split-pr?
Run the command above to copy the skill into ~/.claude/skills/. Claude Code picks it up automatically.
Is mcore-split-pr free?
The code is published under the Apache-2.0 licence. The service it connects to may have its own pricing.
Is mcore-split-pr safe to use?
It scores 94 of 100. Grades: maintenance A, licence A, quality A. Security check: grade A, no risky patterns found in the files checked. Review the code before you install. How grades work.
What are alternatives to mcore-split-pr?
Similar skills: openclaw-github-repo-commander, gradio, replica-launch, e2e-testing-patterns.