brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
run-rust-testsRun Rust tests after making changes to verify correctness
Independent GitHub snapshot · Automated classification · Original documentation governs
Run Rust tests after making changes to verify correctness.
all: Run all Rust tests<crate>: Run tests for specific crate (e.g., /rust-test hyperloglog)<crate> <test>: Run specific test in crate (e.g., /rust-test 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)cd src/redisearch_rs && cargo nextest run -p <crate1> -p <crate2> ...
src/redisearch_rs/, or if you cannot determine affected crates, run all testsall is provided, run all Rust tests:
cd src/redisearch_rs && cargo nextest run
cd src/redisearch_rs && cargo nextest run -p <crate_name>
cd src/redisearch_rs && cargo nextest run -p <crate_name> <test_name>
# Test specific crate
cd src/redisearch_rs && cargo nextest run -p hyperloglog
cd src/redisearch_rs && cargo nextest run -p inverted_index
cd src/redisearch_rs && cargo nextest run -p trie_rs
# Run a specific test
cd src/redisearch_rs && cargo nextest run -p <crate_name> <test_name>
# Run tests under miri (for undefined behavior detection)
cd src/redisearch_rs && cargo +nightly miri test