The request names "mcore-split-pr", which is an indexed action on the NVIDIA source 2: it splits one PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups. Its source page is only a Brev.dev console, so the action is the answer, and the closest tools for splitting PRs into reviewable pieces are GitHub's stacked-PR and combine-PR actions 1.
- 1
NVIDIAnvidia.comverified and signed
The indexed action mcore-split-pr splits a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups 2.
official:MCP server · NVIDIA CUDA Docs+84 community tools built for it
for agents: mcore-split-pr · rapids · pynvvideocodec
- 2
GitHubgithub.comverified and signed
The gh-stack action manages stacked PRs and splits multi-part work into reviewable branches, and github/combine-prs combines multiple PRs into one 1.
official:MCP server · @github/mcp-registrySDK · @github/copilot-sdklibrary · CodeQL: StubCLI · specifyrepository · copilot-engine-sdk+2,577 community tools built for it
for agents: gh-stack · github/combine-prs · my-pull-requests
- 3
PostHogposthog.comfound in code, not yet checked
Its refresh and note PR actions are tracked, but its source does not describe splitting PRs, so this is a weak fit 8.
+16 community tools built for it
for agents: refresh_from_github · propose_topic_change · note_pr
Sources
- 1GitHub · Change is constant. GitHub keeps you ahead. · GitHub · GitHubgithub.com · read 2026-10-29
- 2Brev.dev Consolebrev.nvidia.com · read 2026-10-29
- 8PostHog – Your product’s context layerposthog.com · read 2026-10-29
For agents: the 10 actions behind this answer
gh-stack · gh-stack verified and signed
Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack. Use for stack creation, viewing, edits, push, submit, sync, rebase, merge, or checkout; when asked to split or isolate work for review; whenever a user mentions a stack, branch layers, dependent PRs, or gh stack;
mcore-split-pr · mcore-split-pr verified and signed
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
code-review · code-review verified and signed
Run a final code review on a pull request
Azure/aca-review-apps · Create Azure Container App Review Revisions verified and signed
GitHub Action to create a new Container App revision for PR review. github.com/Azure/Actions
list_pull_request_reviews · issuelens found in code, not yet checked
List one bounded page of reviews on an explicit repository's PR.
pr-review · pr-review verified and signed
Review PyTorch pull requests for code quality, test coverage, security, and backward compatibility. Use when reviewing PRs, when asked to review code changes, or when the user mentions "review PR", "code review", or "check this PR".
PUT /repositories/{workspace}/{repo_slug}/pullrequests/{pull_request_id} · Bitbucket API verified and signed
Update a pull request
refresh_from_github · postpile found in code, not yet checked
mergify · mergify verified and signed
Skills for the Mergify CLI: manage merge queues, stacked pull requests, Test Insights (flaky tests, quarantine), merge protections, and Mergify configuration directly from the terminal.
· Runatlantis website read, tools not yet checked
Atlantis: Terraform Pull Request Automation
Labels are the instruments' verdict and are never changed by ranking. Agents and robots get this same answer as JSON at /api/v1/find?q=…&answer=1 and through the MCP server.