Test rust core
Build and test NeMo Relay Rust core, adaptive, and dynamic plugin crates; use for crates/core, crates/adaptive, crates/plugin, crates/worker, crates/worker-proto, crates/types, or shared runtime changesFrom its SKILL.md
npx -y skills add NVIDIA/NeMo-Relay --skill test-rust-coreAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its file declares
Copied from the file, not written here
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.5 KB, as published. Nobody here has run it
Build And Test Rust Core
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 is primarily in crates/core, crates/adaptive,
dynamic plugin Rust crates, or shared Rust runtime semantics.
Default Path
- Run
cargo fmt --all. - Run
just test-rust. - Run
cargo clippy --workspace --all-targets -- -D warnings. - Because this skill covers
crates/core,crates/adaptive, or shared runtime semantics, expand to the full binding matrix withvalidate-change.
Use narrower crate tests as a local debug loop, not as the final validation story for a Rust change.
Common Commands
# Shared-runtime build/test wrapper
just test-rust
# Required Rust format pass
cargo fmt --all
# Required Rust lint pass
cargo clippy --workspace --all-targets -- -D warnings
# Core runtime only
cargo test -p nemo-relay
# Adaptive crate when touched
cargo test -p nemo-relay-adaptive
# Dynamic plugin crates when touched
just build-test-plugin-fixtures
cargo test -p nemo-relay-types
cargo test -p nemo-relay-plugin
cargo test -p nemo-relay-worker-proto
cargo test -p nemo-relay-worker
cargo test -p nemo-relay --features worker-grpc --test native_plugin_integration --test worker_plugin_integration
# Compile sweep
just build-rust
# Shared-semantics or broad runtime changes
just ci=true test-rust
When To Escalate
- If a public API, event shape, middleware behavior, plugin semantics, or any
crates/core/crates/adaptivebehavior changed, also usevalidate-change. - If native dynamic plugins, gRPC workers,
nemo-relay-plugin,nemo-relay-worker,nemo-relay-worker-proto, ornemo-relay-typeschanged, also usemaintain-dynamic-plugins. - If the change is isolated to one binding wrapper on top of unchanged Rust semantics, prefer that binding's build/test skill instead.
References
Cargo.tomlcrates/core/Cargo.tomlcrates/adaptive/Cargo.tomlcrates/core/README.mdcrates/adaptive/README.mddocs/contribute/testing-and-docs.mdxvalidate-changemaintain-dynamic-plugins