test-ffi-surface
/test-ffi-surface
Build and test the NeMo Relay FFI surface; use this for crates/ffi changes, header generation, or ABI-facing validation
- Author
- dawsonblock ↗
- Repository
- nemo ↗
- Licence
- Apache-2.0
- Last repository change
- 18.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 18.09.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Build and test the NeMo Relay FFI surface; use this for crates/ffi changes, header generation, or ABI-facing validation
Original author description
Build and test the NeMo Relay FFI surface; use this for crates/ffi changes, header generation, or ABI-facing validation
How it works
- Companion Guidance
- Default Path
- Common Commands
- When To Escalate
- References
SKILL.md preview
--- name: test-ffi-surface description: Build and test the NeMo Relay FFI surface; use this for crates/ffi changes, header generation, or ABI-facing validation author: NVIDIA Corporation and Affiliates license: Apache-2.0 --- # Build And Test FFI Surface ## 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 the change is primarily in `crates/ffi`, the generated header, or ABI-facing behavior consumed by Go or external native callers. ## Default Path 1. Rebuild the FFI crate in release mode so the shared library and header stay in sync. 2. Run `cargo fmt --all` because FFI work is Rust work. 3. Run `just test-rust`. 4. Run `cargo clippy --workspace --all-targets -- -D warnings`. 5. Check the generated header diff when any exported symbol or type changed. 6. If downstream consumers changed too, run their binding-specific skills next. ## Common Commands ```bash # Rebuild the shared library with the repo wrapper used by FFI consumers just build-go # Required Rust validation cargo fmt --all just test-rust cargo test -p nemo-relay-ffi cargo clippy --workspace --all-targets -- -D warnings # Review header drift if the FFI surface changed git diff -- crates/ffi/nemo_relay.h ``` ## When To Escalate - If Go behavior changed, also use `test-go-binding`. - If the FFI change reflects shared runtime semantics rather than a pure bridge change, also use `validate-change`. ## References - `crates/ffi/Cargo.toml` - `crates/ffi/build.rs` - `crates/ffi/cbindgen.toml` - `crates/ffi/nemo_relay.h` - `just build-go` - `.pre-commit-config.yaml` - `README.md` - `validate-change`
Versions
The database has no other skills named test-ffi-surface.
Database snapshot: 13.11.2026 · package version fbd007458535 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100test-node-binding
Build and test the NeMo Relay Node.js binding; use this for crates/node changes or Node-facing integration checks - 100test-python-binding
Build and test the NeMo Relay Python binding and worker plugin SDK; use for python/nemo_relay, python/plugin, or crates/python changes - 82ffi-and-language-interop
FFI boundaries: single pointer ownership, opaque handles, null checks, allocate/free pairs, generated C headers, stable ABI and struct layouts, error and context conversion. Use when writing or reviewing native interop. - 95abi-and-calling-conventions
Use when explaining System V AMD64, ARM AAPCS, RISC-V psABI, stack frames, variadic calls, or FFI register rules. Not for the Rust FFI binding layer: use rust-ffi. - 100nemo-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. - 90analyze-rust-ffi-crate-surface
Determine which parts of the C codebase use Rust-defined C symbols. Use this when you want to understand which C code files may be impacted by changes to a Rust FFI crate.