NeMo-Relay

Compare 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

Maintain NeMo Relay package metadata, module paths, generated artifacts, and release-facing build surfaces

Perform a coordinated repository, package, crate, module, or symbol rename across NeMo Relay

Update the NeMo Relay project version across Cargo, Node, and lockfiles without leaving release surfaces out of sync

Choose and run the right NeMo Relay validation matrix for a change instead of using one fixed test list

Debug application-side NeMo Relay integration issues such as load failures, inactive scopes, missing events, or adaptive/plugin wiring problems

Configure and use NeMo Relay OpenInference export for OTLP backends that understand OpenInference semantics

Configure and use NeMo Relay OpenTelemetry export for OTLP-compatible tracing backends

Wrap application tool calls and LLM/provider calls with NeMo Relay scopes and managed execution APIs

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, 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

Choose and set up the right NeMo Relay observability path for an application

Help application developers pick a NeMo Relay binding and get to a first working scope, tool call, and LLM call

Configure the NeMo Relay adaptive plugin component through the shared plugin system; use this skill for state, telemetry, adaptive_hints, tool_parallelism, ACG, or policy settings with validation and measured rollout

Plan a measured NeMo Relay adaptive tuning rollout after baseline scopes, tool calls, LLM calls, and observability are working; use this skill to improve latency, tool parallelism, prompt-cache behavior, or model-request behavior from runtime signals

Use NeMo Relay typed wrappers and codecs without losing middleware behavior

Set up and reason about NeMo Relay scope-stack isolation for concurrent application work

Contribute a new or updated third-party framework integration for NeMo Relay

Maintain and review NeMo Relay GitHub Actions workflows with explicit per-job permissions, pinned action SHAs, deterministic caching, reusable workflow permission boundaries, and local validation

Maintain NeMo Relay dynamic plugin loaders, manifests, Rust native SDKs, gRPC worker protocol, Python worker SDK, docs, tests, and release workflow coverage

Build and test the NeMo Relay Python binding and worker plugin SDK; use for python/nemo_relay, python/plugin, or crates/python changes

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 changes

Export NeMo Relay activity as ATIF trajectories for replay, analysis, or interchange

Consume NeMo Relay adaptive hints, predictions, latency sensitivity, ACG diagnostics, or tool-parallelism guidance safely in application logic after the adaptive plugin is already configured

Prepare a NeMo Relay code freeze by creating the release branch, updating nightly alpha branch config, bumping main to the next version, and opening the required PR

Review documentation, examples, and docs-heavy changes for NVIDIA technical writing style, terminology, and repo accuracy

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

Prepare, open, create, publish, update, or edit a NeMo Relay pull request or PR body with the right tests, docs, contributor hygiene, and repository pull request template

Make a small, reviewable NeMo Relay bug fix without widening scope unnecessarily

Build and test the NeMo Relay FFI surface; use this for crates/ffi changes, header generation, or ABI-facing validation

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

Build and test the NeMo Relay Node.js binding; use this for crates/node changes or Node-facing integration checks

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.