maintain-packaging
Skill238 starsChanged 2 months agoApache-2.0View on GitHub
Add or change NeMo Relay packages, package metadata, module paths, generated artifacts, registry output, or release-facing build surfaces, including registering new unified-release surfaces with version automation. Do not use for a standalone project version bump, ordinary source builds, or tests.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- NVIDIA/NeMo-Fabrictheir own version, first seen Sep 16, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- NVIDIA/NeMo-Fabric★ 73same name
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
- prepare-code-freezeSkill
- prepare-prSkill
- 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
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use this skill when a change affects how NeMo Relay is built, packaged, named, or consumed outside the source tree.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Maintain Release And Packaging Surfaces
Use this skill when a change affects how NeMo Relay is built, packaged, named, or consumed outside the source tree.
Audit Areas
- Rust
Cargo.tomlpackage names and workspace metadata - Python packaging in
pyproject.toml - Python worker plugin SDK packaging in
python/plugin/pyproject.toml - Go module path in
go/nemo_relay/go.mod - Node workspace metadata in root
package.jsonandpackage-lock.json - Node package metadata in
crates/node/package.json - FFI header and library naming
- CI workflows, install commands, and example commands
justfilebuild, test, clean, version, and package recipes for plugin crates and packages- Release tags, release-note surfaces, and registry-facing version translation
Checklist
- Every new package or plugin has an explicit versioning model: either it participates in the unified NeMo Relay release or it has an intentionally independent source of truth
- Package names, import paths, and module names are internally consistent
- Generated artifacts still land where downstream consumers expect
- Docs and examples use the current install/import/build commands
- CI references the same package names as local workflows
- Public packaging changes are reflected in release-facing docs
- For a new unified-release surface, its manifest version, lockfile entry,
and internal NeMo Relay version pins are covered by
set_project_versionin thejustfile; extend the owning helper and its fail-fast field checks in the same change when a value is not derived automatically, without adding a separate test that mirrors the helper's field list nemo-relay-pluginRust and Python packages track the project SemVer policy and Python wheels use valid PEP 440 translation- Release tags still use raw SemVer without a leading
v - Release history and release notes still point to GitHub Releases, not
CHANGELOG.mdor docs pages
References
pyproject.tomlpython/plugin/pyproject.tomlgo/nemo_relay/go.modpackage.jsonpackage-lock.jsoncrates/node/package.jsonRELEASING.md.github/workflows/ci_python.yml.github/workflows/ci.yaml.gitlab-ci.ymljustfile
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.