test-go-binding

от nvidia

Build and test the NeMo Relay Go binding; use this for go/nemo_relay changes or Go-facing integration checks

npx skills add https://github.com/nvidia/nemo-relay --skill test-go-binding

Build And Test Go Binding

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 go/nemo_relay or the Go binding behavior it depends on.

Important Constraint

The Go binding links against the shared FFI library. just test-go builds that library for you, while just build-go remains useful when you want an explicit build-only pass or need the artifact for other work.

Default Path

  1. Format changed Go packages with cd go/nemo_relay && go fmt ./....
  2. Run Go tests with just test-go.
  3. If any Rust files changed as part of the Go work, also run cargo fmt --all, just test-rust, and cargo clippy --workspace --all-targets -- -D warnings.
  4. Use just build-go when you want an explicit build-only pass.
  5. Use just ci=true test-go when you need the CI-style coverage and JUnit path.
  6. Expand to broader validation only if the change touched shared semantics.

Common Commands

# Full Go suite
just test-go

# Format Go files
cd go/nemo_relay && go fmt ./...

# Required when the Go change also touched Rust code
cargo fmt --all
just test-rust
cargo clippy --workspace --all-targets -- -D warnings

# CI-style Go suite with coverage and JUnit artifacts
just ci=true test-go

# Explicit shared-library build when needed separately
just build-go

In the test-go task, the ci variable is what is_true "{{ ci }}" checks. Setting ci=true enables coverage_out and junit_out handling and adds -coverprofile=coverage.out to go_test_cmd.

On macOS, also set DYLD_LIBRARY_PATH to the same ../../target/release directory before running the raw go test command directly.

When To Escalate

  • If the change touched crates/ffi, also use test-ffi-surface.
  • If the change touched crates/core or shared runtime semantics, also use validate-change.

References

  • go/nemo_relay/go.mod
  • go/nemo_relay/nemo_relay.go
  • README.md
  • docs/getting-started/installation.md
  • validate-change

Больше skills от nvidia

compileiq-debug
nvidia
Use when something is wrong: Search() hangs, all evaluations return INVALID_SCORE, scores aren't improving, every config returns the same number, ptxas errors…
official
create-github-pr
nvidia
Create GitHub pull requests using the gh CLI. Use when the user wants to create a new PR, submit code for review, or open a pull request. Trigger keywords -…
official
diagnose-perf
nvidia
First-responder performance triage for Isaac Sim and Isaac Lab. Identifies bottleneck category (GPU-bound, CPU-bound, VRAM, loading) using nvidia-smi and…
official
eagle3-review-logs
nvidia
Review EAGLE3 pipeline experiment logs from the launcher's experiments/ directory. Summarizes pass/fail status for all 4 tasks, diagnoses failures with root…
official
nemoclaw-maintainer-cross-issue-sweep
nvidia
Сканирует другие открытые задачи, чтобы найти те, которые данный PR может исправить или случайно сломать. Выводит возможности смежных исправлений и риски противоречий с указанием файла:строки…
official
karpathy-guidelines
nvidia
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes,…
official
fhir-basics
nvidia
Обучает агентов работе с API FHIR R4, доступным ресурсам, запросам с параметрами поиска и корректному разбору всех форматов ответов…
official
underdeclared-agent
nvidia
A helpful assistant agent
official