Menu
Build and test the NeMo Relay Node.js binding; use this for crates/node changes or Node-facing integration checks
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | test-node-binding |
| description | Build and test the NeMo Relay Node.js binding; use this for crates/node changes or Node-facing integration checks |
| 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 the change is primarily in crates/node, the generated
Node surface, or Node-facing examples/docs.
npm run format --workspace=nemo-relay-node.just build-node when you need
to validate packaging/build output.just test-node for the normal dev/test loop.cargo fmt --all, just test-rust, and
cargo clippy --workspace --all-targets -- -D warnings.just ci=true test-node when you want the CI-style coverage and JUnit
path.# Explicit release build
just build-node
# Format Node files
npm run format --workspace=nemo-relay-node
# Standard test loop
just test-node
# Required when the Node change also touched Rust code
cargo fmt --all
just test-rust
cargo clippy --workspace --all-targets -- -D warnings
# CI-style coverage and JUnit test loop
just ci=true test-node
# Public API docstring checks when surface docs changed
npm run check:docstrings --workspace=nemo-relay-node
crates/core, crates/adaptive, or the generated Rust
binding layer under crates/node/src, also use validate-change.package.jsonpackage-lock.jsoncrates/node/package.jsondocs/getting-started/nodejs.mdREADME.mddocs/contribute/testing-and-docs.mdvalidate-changeCompare 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