What problem does it solve? Running an entire project test suite after every small change wastes time, introduces flaky noise from unrelated tests, and slows down the feedback loop. This Skill enforces a targeted test execution policy so only tests relevant to the modified files or commits are run. ## Core Features & Use Cases - Change-based test selection: Identifies affected classes and packages from git log and git diff output, then maps them to the corresponding test files. - Multi-runner filter commands: Provides ready filtering syntax for Gradle (--tests), pytest (-k, node IDs), jest (-t, file paths), go test (-run), and cargo test. - Layer-scoped execution: Runs only domain-layer tests for domain changes, infrastructure-layer tests for infrastructure changes, and so on. - Defined exceptions: Specifies exactly when a full suite run is allowed, such as explicit user requests, large refactorings, or the single pre-commit full run required by the superpowers implementer contract. - Use Case: After editing a single service class, use this Skill to run only that class's tests with gradlew test --tests "*ServiceTest" instead of a 10-minute full suite. ## Quick Start Run only the tests affected by my latest commit instead of the full test suite, and show me the command and raw output.