What problem does it solve? Teams often write tests at the wrong level or with the wrong style for the code being tested, such as mocking pure transformations or asserting interactions on stateful objects. This Skill reviews whether the testing strategy fits the problem class of the production code and reports concrete mismatches. ## Core Features & Use Cases - Problem class classification: Classifies each tested behavior as Transformation, Stateful Object, or Integration, with a mandatory user confirmation gate before any recommendation. - Strategy comparison: Identifies the current test strategy (output-based, state-based, or interaction-based) and compares it against the recommended strategy for the confirmed problem class. - Structured mismatch report: Produces a per-test-class report with problem class, current strategy, recommended strategy, and an OK or MISMATCH verdict with concrete change guidance. - Use Case: Point the Skill at a test file for an order checkout service; it reads both the test and production code, classifies the orchestration as Integration, and flags that mocking the managed database should be replaced with a real instance and state verification. ## Quick Start Ask the assistant to review the test strategy for a specific test file or directory, providing the path to the tests you want evaluated.
