mcore-split-pr SKILL.md skillA
mcore-split-pr from nvidia/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add nvidia/skills/mcore-split-pr@git:20260529.416539cPins git:20260529.416539c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- nvidia/skills
- Path
skills/mcore-split-pr/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260529.416539c, committed May 29, 2026
- Size
- 4,484 bytes
- Repository stars
- 3,871
- License
- Apache-2.0
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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 …
Read the whole file at its exact version.
How to install
mdr add nvidia/skills/mcore-split-pr@sha256:0f3d40922d3c57ebThe line at the top of this page pins the label git:20260529.416539c, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_7vjyvktaluisd22i)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on May 29, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4484 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nvidia/skills · 3,871 stars · license Apache-2.0 · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7vjyvktaluisd22i GET https://markdownregistry.com/api/v1/resolve?ref=nvidia/skills/mcore-split-pr GET https://markdownregistry.com/api/v1/blob/0f3d40922d3c57eb6eba1ed74b8b6cdb3e87a469c1e6afd41541d2fed72e21a0
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.