rename-surfaces
FeaturedRename a NeMo Relay repository, package, crate, module, public symbol, import path, or brand surface across multiple consumers. Do not use for a file-local private rename.
Install
Quality Score: 87/100
Skill Content
Details
- Author
- NVIDIA
- Repository
- NVIDIA/NeMo-Relay
- Created
- 5 months ago
- Last Updated
- today
- Language
- Rust
- License
- Apache-2.0
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
maintain-packaging
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.
rebrand
Safely rebrands a product across a repository — audits every old-brand occurrence, replaces only the safe ones, and validates the result. Invoke as /skill:rebrand OldName -> NewName.
nemo-relay-migrate-from-flow
Use this skill when migrating applications, examples, integrations, documentation, manifests, or repository code from NeMo Flow to NeMo Relay across Python, Rust, Node.js, Go, C FFI, CLI, configuration, and observability surfaces.