prepare-pr
Skill238 starsChanged 2 months agoApache-2.0View on GitHub
Prepare, create, publish, or edit a NeMo Relay pull request or its body using the repository template and contributor requirements. Do not use for code review or implementation without PR preparation.
- Commits and pushes
12 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- dativo-io/talontheir own version, first seen Oct 25, 2026
- WikiEducationFoundation/WikiEduDashboardtheir own version, first seen Oct 9, 2026
- TermiX-official/cryptoclawtheir own version, first seen Oct 8, 2026
- mengxi-ream/read-frogtheir own version, first seen Oct 8, 2026
- chattymin/PokeTokenBartheir own version, first seen Oct 5, 2026
- atsushi-green/ds-ai-coding-skillstheir own version, first seen Sep 25, 2026
Used with
Projects with it also use review-pr.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
DockerSkillreview-pr
Review one or more incoming Docker documentation pull requests as a maintainer. Independently validate technical claims, assess editorial fit and information architecture, choose a verdict, and draft exact inline or PR-wide feedback behind a confirmation gate. Use for requests such as "review PR 123", "is this PR correct?", "does this information belong here?", "validate this PR", or "help review backlog PRs". Do not use to maintain or fix a PR you own; use maintain-pr for that.
Also in 3 projects that use this
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- NVIDIA/NeMo-Fabric★ 7358% same
Wrote their own version · 11
- mengxi-ream/read-frog★ 10ksame name
- chattymin/PokeTokenBar★ 557same name
- WikiEducationFoundation/WikiEduDashboard★ 431same name
- TermiX-official/cryptoclaw★ 100same name
- atsushi-green/ds-ai-coding-skills★ 86same name
- neul-labs/openclawMU★ 33same name
- dativo-io/talon★ 18same name
- pnnl/adept-agentic★ 2same name
- andreilupu/my-claude-skills★ 1same name
- briansu2004/MyAgentSkills★ 1same name
1 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository30 other files it gives its agents.
- AGENTS.mdAGENTS.md
- add-binding-featureSkill
- add-middlewareSkill
- check-release-deploymentsSkill
- contribute-docsSkill
- contribute-integrationSkill
- create-beta-tagSkill
- create-rc-tagSkill
- create-release-tagSkill
- draft-release-notesSkill
- maintain-ciSkill
- maintain-dynamic-pluginsSkill
- maintain-observabilitySkill
- maintain-optimizerSkill
- maintain-packagingSkill
- prepare-code-freezeSkill
- rename-surfacesSkill
- review-doc-styleSkill
- update-project-versionSkill
- nemo-relay-debug-runtime-integrationSkill
- nemo-relay-get-startedSkill
- nemo-relay-installSkill
- nemo-relay-instrument-callsSkill
- nemo-relay-instrument-context-isolationSkill
- nemo-relay-instrument-typed-wrappersSkill
- nemo-relay-integrate-upstreamSkill
- nemo-relay-migrate-from-flowSkill
- nemo-relay-plugin-adaptive-tuningSkill
- nemo-relay-plugin-buildSkill
- nemo-relay-plugin-observabilitySkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 8 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use this skill at the end of a contributor or maintainer change before opening a pull request.
- Distinctive: line 14
If this repo-local guidance conflicts with generic GitHub publishing, connector, or plugin guidance, this skill wins for PR body format, …
- Distinctive: line 30
Use Conventional Commit style for PR titles:
- Very specific: line 54
Always use .github/pull_request_template.md as the source of truth for the PR body.
- Distinctive: line 62
When using GitHub CLI, prefer:
- Distinctive: line 68
If a tool cannot consume the template directly, create the PR body from the template content and then fill in every visible section before …
- Distinctive: line 70
Do not replace the template with a freeform summary.
- Distinctive: line 72
After creating or editing a PR, fetch the rendered PR body and verify that the template's visible headings and checklist items are still …
- Distinctive: line 86
Only check the contribution confirmation boxes when they are true.
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Prepare A PR For NeMo Relay
Use this skill at the end of a contributor or maintainer change before opening a pull request. Also use it whenever a user asks to create, open, publish, update, or edit a NeMo Relay pull request, pull request description, or PR body.
If this repo-local guidance conflicts with generic GitHub publishing, connector, or plugin guidance, this skill wins for PR body format, validation language, and review handoff details.
Checklist
- Branch scope is coherent and reviewable
- Validation results accurately report checks already run and relevant omissions without widening validation solely for PR preparation
- Pull request title follows Conventional Commit style and uses the correct type
- Pull request body follows
.github/pull_request_template.md - Breaking changes or renamed surfaces are called out explicitly
Pull Request Title
Use Conventional Commit style for PR titles:
<type>: <concise imperative summary>Choose the type from the actual change surface, not from the impact of the
review comment or CI outcome. Use fix only for an actual user-facing or
runtime/product code bug fix. Never use fix for changes that are not related
to product code behavior, including chores, CI configuration, docs, tests,
packaging metadata, generated-output handling, or agent/skill guidance.
Common examples:
ci: update codecov coverage reportingdocs: clarify release workflowenhancement: improve scope configurationchore: refresh generated attribution dataskills: add a plugin-authoring guidetest: add Python scope regression coveragefix: preserve scope-local middleware cleanup
Opening A Pull Request
Always use .github/pull_request_template.md as the source of truth for the PR
body. Before opening a PR, read the current template and preserve its headings,
checkboxes, comments' intent, and related-issue guidance.
This applies both when creating a new PR and when editing an existing PR
description. Do not use a generic Summary / Why / Validation body unless the
current repository template uses those headings.
When using GitHub CLI, prefer:
gh pr create --template .github/pull_request_template.mdIf a tool cannot consume the template directly, create the PR body from the template content and then fill in every visible section before opening the PR. Do not replace the template with a freeform summary.
After creating or editing a PR, fetch the rendered PR body and verify that the template's visible headings and checklist items are still present.
The PR body must include:
#### Overviewwith a concise summary and both contribution confirmation checklist items preserved#### Detailswith the concrete changes made#### Where should the reviewer start?with the most useful file, test, or design decision#### Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)with an issue reference, or a clearRelates to: noneentry when there is no related issue
Only check the contribution confirmation boxes when they are true. If either confirmation cannot be made, stop before opening the PR and surface the blocker.
References
CONTRIBUTING.md.github/pull_request_template.md
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.