rust-test-quality-review

Reviews whether Rust tests prove changed behavior, covering assertions, regression gaps, and determinism.

2|Updated May 6, 2026
One-click install
npx skills add https://github.com/bpcakes/jig-skills --skill rust-test-quality-review-bpcakes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rust-test-quality-review
Source: https://github.com/bpcakes/jig-skills/tree/main/plugins/jig-rust/skills/rust-test-quality-review
Command: npx skills add https://github.com/bpcakes/jig-skills --skill rust-test-quality-review-bpcakes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often ship with tests that pass but do not actually prove the new behavior, leaving regressions undetected. This Skill audits Rust tests against the behavioral contracts in a diff to find coverage gaps, weak assertions, and lost protections. ## Core Features & Use Cases - Coverage and regression analysis: Traces changed behavior to its tests, identifies plausible regressions the existing suite would accept, and flags removed tests, broadened matchers, or new #[ignore] gates that silently drop protection. - Assertion and oracle quality checks: Detects tautological assertions, imprecise float comparisons, overly broad #[should_panic] tests, and mocks that bypass the behavior under test. - Isolation and determinism review: Examines shared state, environment dependencies, async interleavings, and feature-gated behavior for nondeterministic failures. - Use Case: After refactoring error handling in a Rust service, ask for a test quality review of the working changes to learn which error variants lack regression tests before merging. ## Quick Start Ask the agent to review whether the tests in your current staged and unstaged Rust changes actually prove the changed behavior, and to report findings with file locations without editing code.

Frequently Asked Questions about rust-test-quality-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if my Rust tests actually cover my code changes?

Request a test quality review of your staged and unstaged changes. The review maps each changed behavioral contract to its tests, identifies regressions the current suite would accept, and suggests focused tests with file locations.

How to review Rust test assertions for weak or tautological checks?

The review inspects whether each assertion uses an oracle independent of the implementation and is sensitive to the relevant failure. It flags self-confirming comparisons, overly broad should_panic tests, and cases where is_ok() hides a missing contract check.

Does this review modify my Rust test files?

No. For a review-only request it reports findings and test suggestions without changing files. Tests are only added or repaired when implementation is explicitly part of the user's task.

Can it detect removed or disabled Rust tests in a diff?

Yes. It compares base and final diffs for removed tests or assertions, broadened matchers, new ignore attributes or cfg gates, and CI filter changes, then identifies which previously rejected regression would now pass or never execute.

What are the limitations of a static Rust test quality review?

Static inspection cannot measure actual coverage, so the review distinguishes inspection from measured results and states verification limits. A before/after test run or targeted mutation can strengthen confidence only when authorized and isolated.