mujoco-rs

Build rustdoc and Sphinx documentation, verifying both for warnings, broken links, content correctness, and changelog/migration completeness against the code. Use this when asked to build docs, check doc comments, or verify documentation.

Pre-release preparation and verification workflow for cutting a new mujoco-rs version. Use this when asked to prepare a release, do a pre-release check, cut version X.Y.Z, or verify the crate is ready to publish. Runs every gate the maintainer needs before publishing, then hands off the networked publish steps.

Systematically verify correctness of the mujoco-rs wrapper layer using parallel subagents. Use this when asked to audit, verify, or deeply check the codebase for bugs.

Audit the impact of regenerated MuJoCo FFI bindings (the ffi-regenerate Cargo feature) on the wrapper layer. Diffs src/mujoco_c.rs, reads the MuJoCo changelog entries for the version range, deep-verifies every changed item against the C/C++ source, and writes a self-contained HTML report suggesting required wrapper additions/removals/updates. Strictly read-only -- it suggests changes but never edits code. Use after regenerating the FFI bindings or bumping the MuJoCo version.

Adversarial multi-agent soundness audit of the mujoco-rs SAFE API surface -- memory safety, thread safety (every unsafe impl Send/Sync), &self vs &mut self mutability, and lifetime/variance correctness, restricted to defects reachable from 100% safe code. Produces a single self-contained HTML report. Use when asked to audit/check the crate for unsoundness or undefined behavior reachable from safe code. Distinct from /verify (which covers stride/length-field/type correctness).

Run AddressSanitizer and UndefinedBehaviorSanitizer on the Rust+C FFI boundary. Use this when asked to check for memory errors, undefined behavior, or when verifying FFI safety.

Build the mujoco-rs library using the pre-downloaded MuJoCo shared library. Use this when asked to build or compile the project.

Run cargo clippy for Rust linting. Use this when asked to lint the code or check for common mistakes.

Run the codebase under Miri with native FFI support to detect undefined behavior in Rust-C interop. Use this when asked to check for UB or verify memory safety.

Compile and run one of the example programs. Use this when asked to run an example or demo.

Run the in-crate unit tests for mujoco-rs. Use this when asked to run tests or verify that changes work correctly.

Build MuJoCo from the mujoco/ submodule as a WebAssembly static library and run an example under Node.js via Emscripten. Use this when asked to build for WebAssembly / WASM / Emscripten, or to run examples in Node.js.