Run Rust tests after making changes to verify correctness. Use this when you want to verify your changes to Rust code.
63
74%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.skills/run-rust-tests/SKILL.mdRun Rust tests after making changes to verify correctness.
all: Run all Rust tests<crate>: Run tests for specific crate (e.g., /run-rust-tests hyperloglog)<crate> <test>: Run specific test in crate (e.g., /run-rust-tests hyperloglog test_merge)Arguments provided: $ARGUMENTS
Run this skill after modifying Rust code to ensure tests pass.
src/redisearch_rs/ using git status and git diff --name-onlysrc/redisearch_rs/, e.g., src/redisearch_rs/hyperloglog/src/lib.rs → hyperloglog)cargo nextest run --manifest-path src/redisearch_rs/Cargo.toml -p <crate1> -p <crate2> ...src/redisearch_rs/, or if you cannot determine affected crates, run all testsall is provided, run all Rust tests:
cargo nextest run --manifest-path src/redisearch_rs/Cargo.tomlcargo nextest run --manifest-path src/redisearch_rs/Cargo.toml -p <crate_name>cargo nextest run --manifest-path src/redisearch_rs/Cargo.toml -p <crate_name> <test_name># Test specific crate
cargo nextest run --manifest-path src/redisearch_rs/Cargo.toml -p hyperloglog
cargo nextest run --manifest-path src/redisearch_rs/Cargo.toml -p inverted_index
cargo nextest run --manifest-path src/redisearch_rs/Cargo.toml -p trie_rs
# Run a specific test
cargo nextest run --manifest-path src/redisearch_rs/Cargo.toml -p <crate_name> <test_name>
# Run tests under miri (for undefined behavior detection)
cargo +nightly miri test --manifest-path src/redisearch_rs/Cargo.toml75d5559
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.