smithery.ai

run-rust-tests

Run Rust tests after making changes to verify correctness. Use this when you want to verify your changes to Rust code.

First seen Mar 22, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,494 B
  • docs SUMMARY.md 79 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

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/redisearchrs/ using git status and git diff --name-only 2. Map each modified file to its crate (the directory name directly under src/redisearchrs/, e.g., src/redisearchrs/hyperloglog/src/lib.rs → hyperloglog) 3. Run tests for each affected crate: ``bash cargo nextest run --manifest-path src/redisearchrs/Cargo.toml -p <crate1> -p <crate2> ... ` 4. If no Rust files were modified in src/redisearchrs/, or if you cannot determine affected crates, run all tests - If all is provided, run all Rust tests: `bash cargo nextest run --manifest-path src/redisearchrs/Cargo.toml ` - If a crate name is provided, run tests for that crate: `bash cargo nextest run --manifest-path src/redisearchrs/Cargo.toml -p <cratename> ` - If both crate and test name are provided, run the specific test: `bash cargo nextest run --manifest-path src/redisearchrs/Cargo.toml -p <cratename> <test_name> ``

  1. 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
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.toml