RediSearch / run-rust-tests
Install for your project team
Run this command in your project directory to install the skill for your entire team:
mkdir -p .claude/skills/run-rust-tests && curl -L -o skill.zip "https://fastmcp.me/Skills/Download/3745" && unzip -o skill.zip -d .claude/skills/run-rust-tests && rm skill.zipProject Skills
This skill will be saved in .claude/skills/run-rust-tests/ and checked into git. All team members will have access to it automatically.
Important: Please verify the skill by reviewing its instructions before using it.
Run Rust tests after making changes to verify correctness
0 views
0 installs
Skill Content
---
name: run-rust-tests
description: Run Rust tests after making changes to verify correctness. Use this when you want to verify your changes to Rust code.
---
# Rust Test Skill
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
1. Check the arguments provided above:
- If arguments are empty, determine affected crates:
1. Check which files were modified in `src/redisearch_rs/` using `git status` and `git diff --name-only`
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`)
3. Run tests for each affected crate:
```bash
cd src/redisearch_rs && cargo nextest run -p <crate1> -p <crate2> ...
```
4. 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:
```bash
cd src/redisearch_rs && cargo nextest run
```
- If a crate name is provided, run tests for that crate:
```bash
cd src/redisearch_rs && cargo nextest run -p <crate_name>
```
- If both crate and test name are provided, run the specific test:
```bash
cd src/redisearch_rs && cargo nextest run -p <crate_name> <test_name>
```
2. 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
```bash
# 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
```