Check Rust Coverage

What it does

This skill allows AI agents to verify code coverage metrics specifically for Rust projects. It executes coverage analysis tools to determine how much of the source code is exercised by existing tests, ensuring quality assurance in backend development workflows.

When to use it

• Before merging a pull request to confirm new test cases adequately cover added logic.
• During CI/CD pipelines to enforce minimum coverage thresholds for Rust services.
• When auditing legacy codebases to identify untested modules requiring attention.
• To generate reports for stakeholders on the current state of test reliability.

Key capabilities

• Analyzes Rust source code and associated test suites.
• Calculates specific line, function, or branch coverage percentages.
• Identifies uncovered lines or functions within the project structure.
• Integrates directly into automated testing workflows for immediate feedback.

Example prompts

• "Run a coverage check on my Rust backend service and summarize which modules have less than 80% coverage."
• "Compare the code coverage of the main branch against the feature branch to see if new tests were added."
• "List all uncovered functions in the auth module of this Rust project."

Tips & gotchas

Ensure your Rust project has a compatible test runner (like cargo) configured before invoking this skill, as it relies on standard coverage tools. Coverage metrics can vary based on how the tool is configured; specify flags if you need specific report formats or thresholds.