Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

Começar

maintain-packaging

Estrelas73

Forks40

Atualizado1 de julho de 2026 às 15:57

Maintain NeMo Relay package metadata, module paths, generated artifacts, and release-facing build surfaces

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

NVIDIA

NVIDIA/NeMo-Relay

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

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

Maintain Release And Packaging Surfaces

Companion Guidance

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.

Audit Areas

Rust Cargo.toml package 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.json and package-lock.json
Node package metadata in crates/node/package.json
FFI header and library naming
CI workflows, install commands, and example commands
justfile build, test, clean, version, and package recipes for plugin crates and packages
Release tags, release-note surfaces, and registry-facing version translation

Checklist

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
nemo-relay-plugin Rust 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.md or docs pages

References

pyproject.toml
python/plugin/pyproject.toml
go/nemo_relay/go.mod
package.json
package-lock.json
crates/node/package.json
RELEASING.md
.github/workflows/ci_python.yml
.github/workflows/ci.yaml
.gitlab-ci.yml
maintain-dynamic-plugins

Mais deste repositório

mesmo repositório

draft-release-notes

NVIDIA/NeMo-Relay

Compare 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.

2026-07-0873

contribute-docs

NVIDIA/NeMo-Relay

Contribute documentation or example changes that stay aligned with NeMo Relay public behavior

2026-07-0273

nemo-relay-build-plugin

NVIDIA/NeMo-Relay

Build and package reusable NeMo Relay runtime behavior as a config-activated plugin with validation and rollback-safe registration

2026-07-0273

add-binding-feature

NVIDIA/NeMo-Relay

Add or change a public NeMo Relay API surface across the core runtime and every affected binding

2026-07-0173

maintain-observability

NVIDIA/NeMo-Relay

Maintain or extend NeMo Relay observability surfaces across ATIF, OpenTelemetry, and OpenInference

2026-07-0173

maintain-optimizer

NVIDIA/NeMo-Relay

Maintain or extend the NeMo Relay adaptive surface across config, plugins, docs, and bindings; use this when users still say optimizer

2026-07-0173

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

Maintain Release And Packaging Surfaces

Companion Guidance

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.

Audit Areas

Rust Cargo.toml package 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.json and package-lock.json
Node package metadata in crates/node/package.json
FFI header and library naming
CI workflows, install commands, and example commands
justfile build, test, clean, version, and package recipes for plugin crates and packages
Release tags, release-note surfaces, and registry-facing version translation

Checklist

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
nemo-relay-plugin Rust 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.md or docs pages

References

pyproject.toml
python/plugin/pyproject.toml
go/nemo_relay/go.mod
package.json
package-lock.json
crates/node/package.json
RELEASING.md
.github/workflows/ci_python.yml
.github/workflows/ci.yaml
.gitlab-ci.yml
maintain-dynamic-plugins