check-rust-coverage
Detects and lists specific lines of Rust code not covered by existing tests.
Install
mkdir -p .claude/skills/check-rust-coverage && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/1049" && unzip -o skill.zip -d .claude/skills/check-rust-coverage && rm skill.zipInstalls to .claude/skills/check-rust-coverage
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Check which Rust lines are not covered by Rust tests. Use this when you developed new Rust code and want to ensure it is tested.Key capabilities
- →Run coverage analysis on Rust crates
- →Identify untested lines of code
- →Output uncovered line numbers
How it works
It executes cargo llvm-cov to generate coverage data and filters the JSON output to display lines with zero hits.
Inputs & outputs
When to use check-rust-coverage
- →Check test coverage for new crate features
- →Identify untested edge cases in source code
- →Audit project test maturity
About this skill
Check Rust Coverage
Determine which Rust lines are not covered by Rust tests.
Arguments
<path>: Path to a Rust crate.<path 1> <path 2>: Multiple crate paths.
If a path doesn't include src/, assume it to be in the src/redisearch_rs directory. E.g. numeric_range_tree becomes src/redisearch_rs/numeric_range_tree.
If a path points to a directory, consider all Rust crates in that directory.
Instructions
Run
cargo llvm-cov test --manifest-path <crate_directory>/Cargo.toml --quiet --json 2>/dev/null | jq -r '"Uncovered Lines:",
(.data[0].files[] |
select(.summary.lines.percent < 100) |
.filename as $f |
[.segments[] | select(.[2] == 0 and .[4] == true) | .[0]] |
unique |
if length > 0 then "\($f): \(join(", "))" else empty end
)'
to get the list of uncovered lines for each file in the target crate.
When not to use it
- →When the project is not a Rust crate
- →When tests are not configured for the target
Prerequisites
Limitations
- →Requires cargo-llvm-cov installation
- →Only works for Rust projects
How it compares
It provides a direct, automated path to identifying specific untested lines rather than relying on manual coverage report inspection.
Compared to similar skills
check-rust-coverage side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| check-rust-coverage (this skill) | 5 | 5mo | Review | Beginner |
| rust-tests-guidelines | 7 | 5mo | No flags | Beginner |
| check-code-quality | 1 | 28d | Review | Advanced |
| lint | 1 | 2mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by RediSearch
View all by RediSearch →You might also like
rust-tests-guidelines
RediSearch
Guidelines for writing Rust tests.
check-code-quality
r3bl-org
Run comprehensive Rust code quality checks including compilation, linting, documentation, and tests. Use after completing code changes and before creating commits.
lint
RediSearch
Check code quality and formatting before committing changes
run-clippy
r3bl-org
Run clippy linting, enforce comment punctuation rules, format code with cargo fmt, and verify module organization patterns. Use after code changes and before creating commits.
move-code-quality
davila7
Analyzes Move language packages against the official Move Book Code Quality Checklist. Use this skill when reviewing Move code, checking Move 2024 Edition compliance, or analyzing Move packages for best practices. Activates automatically when working with .move files or Move.toml manifests.
pre_commit
pums974
Standardized pre-commit workflow for linting, formatting, and local quality gates.