What problem does it solve? Engineers often struggle to decide which tests and validation checks are worth running for a given change, leading to either over-testing with slow, brittle suites or under-testing that ships unverified behavior. This Skill provides consistent guidance for choosing the right validation, tying it to the behavior being changed, and reporting residual risk honestly. ## Core Features & Use Cases - Validation Selection: Recommends the most relevant checks for a change, preferring focused, high-signal tests over broad, expensive rituals. - Test Design Guidance: Advises when to use unit tests for isolated logic, integration tests for boundaries, and end-to-end checks for user-critical flows. - Risk Reporting: Distinguishes verified behavior from assumed behavior and clearly states what remains uncertain when full validation is not possible. - Use Case: After modifying a database seeding engine's checksum logic, use this Skill to decide which unit and integration tests to add, which existing tests to update, and how to communicate any unverified edge cases to reviewers. ## Quick Start Ask the assistant to review your recent code change and recommend which tests and validation checks to run before merging.
