What problem does it solve? Test suites accumulate change-detector tests that mirror the code under test, break on any behavior-preserving refactor, and catch no real defects. This Skill identifies those tautological tests and guides you to rewrite them against real behavioral contracts or delete them safely. ## Core Features & Use Cases - Litmus Test for New Tests: Apply a three-question check (derivative, refactor-fragile, no oracle) before keeping any newly written test. - Pattern Checklist for Sweeps: Systematically scan existing tests for seven anti-patterns including checksum assertions, echo assertions, duplicate-algorithm tests, snapshots without an oracle, and mock-theater call-graph transcription. - Rewrite-or-Delete Decision Framework: For each flagged test, find the contract it should protect, then rewrite assertions against observable behavior or delete tests with no contract while preserving coverage of critical logic. - Use Case: After a behavior-preserving refactor breaks dozens of tests, run a sweep over the affected test files to separate genuine regression signals from change-detector noise, then rewrite or delete the offenders. ## Quick Start Review the tests in src/services and flag any tautological tests that just mirror the implementation, then rewrite or delete them.
