What problem does it solve?
It challenges unit tests that appear to “pass” while secretly validating the implementation instead of the intended specification, helping you avoid false confidence from brittle or tautological tests.
Core Features & Use Cases
- False-positive test detection: Identifies patterns where the oracle comes from running the code rather than independent domain truth.
- Verdict-driven auditing: Classifies tests as Solid, Suspicious, Likely False Positive, or Vacuous based on a catalog of challenge patterns.
- Test remediation guidance: Recommends fixes such as independent oracle rewrites, boundary/negative test additions, property-based testing, or deletion of vacuous tests.
- Use case: Review AI-generated or coverage-driven tests that increased line coverage but may be mirroring bugs instead of verifying correct behavior.
Quick Start
Ask the skill to challenge your tests by providing the test file(s) and the source file(s) they are intended to validate, and request a pattern-based verdict plus remediation steps.