ワンクリックで
maintain-packaging
Maintain NeMo Relay package metadata, module paths, generated artifacts, and release-facing build surfaces
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Maintain NeMo Relay package metadata, module paths, generated artifacts, and release-facing build surfaces
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | maintain-packaging |
| description | Maintain NeMo Relay package metadata, module paths, generated artifacts, and release-facing build surfaces |
| author | NVIDIA Corporation and Affiliates |
| license | Apache-2.0 |
Use karpathy-guidelines alongside this skill for implementation or review
work. Keep changes scoped, surface assumptions, and define focused validation
before editing.
Use this skill when a change affects how NeMo Relay is built, packaged, named, or consumed outside the source tree.
Cargo.toml package names and workspace metadatapyproject.tomlpython/plugin/pyproject.tomlgo/nemo_relay/go.modpackage.json and package-lock.jsoncrates/node/package.jsonjustfile build, test, clean, version, and package recipes for plugin crates
and packagesnemo-relay-plugin Rust and Python packages track the project SemVer
policy and Python wheels use valid PEP 440 translationvCHANGELOG.md or docs pagespyproject.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.ymlmaintain-dynamic-pluginsCompare NeMo Relay release branches and draft or update the documentation-site release notes. Use when preparing a release-notes update under docs/about-nemo-relay/release-notes, reviewing release-to-release changes, or gathering evidence for a current release summary.
Contribute documentation or example changes that stay aligned with NeMo Relay public behavior
Build and package reusable NeMo Relay runtime behavior as a config-activated plugin with validation and rollback-safe registration
Add or change a public NeMo Relay API surface across the core runtime and every affected binding
Maintain or extend NeMo Relay observability surfaces across ATIF, OpenTelemetry, and OpenInference
Maintain or extend the NeMo Relay adaptive surface across config, plugins, docs, and bindings; use this when users still say optimizer