Run Rust tests after making changes to verify correctness.
Arguments
No arguments: Analyze changes and run tests for affected crates only
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
Usage
Run this skill after modifying Rust code to ensure tests pass.
Instructions
Check the arguments provided above:
If arguments are empty, determine affected crates:
Check which files were modified in src/redisearch_rs/ using git status and git diff --name-only
Map each modified file to its crate (the directory name directly under src/redisearch_rs/, e.g., src/redisearch_rs/hyperloglog/src/lib.rs → hyperloglog)
Run tests for each affected crate:
cd src/redisearch_rs && cargo nextest run -p <crate1> -p <crate2> ...
If no Rust files were modified in src/redisearch_rs/, or if you cannot determine affected crates, run all tests
If all is provided, run all Rust tests:
cd src/redisearch_rs && cargo nextest run
If a crate name is provided, run tests for that crate:
cd src/redisearch_rs && cargo nextest run -p <crate_name>
If both crate and test name are provided, run the specific test:
cd src/redisearch_rs && cargo nextest run -p <crate_name> <test_name>
If tests fail:
Read the error output carefully
Fix the failing tests or the code causing failures
Re-run tests to verify the fix
Common Test Commands
# 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
1---2name: run-rust-tests3description: Rust Test Skill4---5# Rust Test Skill67Run Rust tests after making changes to verify correctness.89## Arguments10- No arguments: Analyze changes and run tests for affected crates only11- `all`: Run all Rust tests12- `<crate>`: Run tests for specific crate (e.g., `/run-rust-tests hyperloglog`)13- `<crate> <test>`: Run specific test in crate (e.g., `/run-rust-tests hyperloglog test_merge`)1415Arguments provided: `$ARGUMENTS`1617## Usage18Run this skill after modifying Rust code to ensure tests pass.1920## Instructions21221. Check the arguments provided above:23 - If arguments are empty, determine affected crates:24 1. Check which files were modified in `src/redisearch_rs/` using `git status` and `git diff --name-only`25 2. Map each modified file to its crate (the directory name directly under `src/redisearch_rs/`, e.g., `src/redisearch_rs/hyperloglog/src/lib.rs` → `hyperloglog`)26 3. Run tests for each affected crate:27 ```bash28 cd src/redisearch_rs && cargo nextest run -p <crate1> -p <crate2> ...29 ```30 4. If no Rust files were modified in `src/redisearch_rs/`, or if you cannot determine affected crates, run all tests31 - If `all` is provided, run all Rust tests:32 ```bash33 cd src/redisearch_rs && cargo nextest run34 ```35 - If a crate name is provided, run tests for that crate:36 ```bash37 cd src/redisearch_rs && cargo nextest run -p <crate_name>38 ```39 - If both crate and test name are provided, run the specific test:40 ```bash41 cd src/redisearch_rs && cargo nextest run -p <crate_name> <test_name>42 ```432. If tests fail:44 - Read the error output carefully45 - Fix the failing tests or the code causing failures46 - Re-run tests to verify the fix4748## Common Test Commands4950```bash51# Test specific crate52cd src/redisearch_rs && cargo nextest run -p hyperloglog53cd src/redisearch_rs && cargo nextest run -p inverted_index54cd src/redisearch_rs && cargo nextest run -p trie_rs5556# Run a specific test57cd src/redisearch_rs && cargo nextest run -p <crate_name> <test_name>5859# Run tests under miri (for undefined behavior detection)60cd src/redisearch_rs && cargo +nightly miri test61```
Run npx skillmds@latest add comeonoliver/run-rust-tests in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Rust Test Skill It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
ComeOnOliver (@comeonoliver) published this skill. Their other Agent Skills are listed on their SkillMD profile.
ComeOnOliver