// Contribute documentation or example changes that stay aligned with NeMo Relay public behavior
Migrate applications, examples, integrations, documentation, package manifests, and repository code from NeMo Flow naming and packages to NeMo Relay across Python, Rust, Node.js, Go, WebAssembly, C FFI, CLI, config, and observability surfaces; use when a user asks to rename nemo_flow/nemo-flow/NeMo Flow APIs, automate a migration, update imports or dependencies, or validate a Flow-to-Relay conversion
Add or change a public NeMo Relay API surface across the core runtime and every affected binding
Add a new third-party framework integration maintained as a NeMo Relay patch set
Add a new guardrail or intercept type to the NeMo Relay middleware pipeline
Contribute a new NeMo Relay public API surface safely, with binding parity and docs in mind
Contribute a new or updated third-party framework integration for NeMo Relay
| name | contribute-docs |
| description | Contribute documentation or example changes that stay aligned with NeMo Relay public behavior |
| 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 for docs-only or example-heavy changes.
RELEASING.md, not as user-facing docs pages or CHANGELOG.mdscripts/ root in docs and examples;
only point at namespaced helper paths when documenting internal maintenance
workREADME.md or docs/index.md updated when entry points changedREADME.md files updated when examples or binding guidance changedjust docs when the docs site changed; ./scripts/build-docs.sh html remains the compatibility wrapperCONTRIBUTING.mdRELEASING.mddocs/contribute/testing-and-docs.mdreview-doc-style