test-targeted

Narrows test execution to tests affected by recent code changes across Gradle, pytest, jest, and go test.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/Hakkadaikon/hymme --skill test-targeted-hakkadaikon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-targeted
Source: https://github.com/Hakkadaikon/hymme/tree/main/skills/test-targeted
Command: npx skills add https://github.com/Hakkadaikon/hymme --skill test-targeted-hakkadaikon

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about test-targeted

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run only tests related to my code changes?

Identify modified classes and packages with git log and git diff, then pass them to your test runner's filter option. For example, use gradlew test --tests "*ClassNameTest" or pytest path/to/test_file.py to run only the affected tests.

How to filter tests in Gradle, pytest, and jest?

Gradle uses --tests "FQCN" or wildcard patterns, pytest accepts node IDs like file.py::TestClass::test_func or -k expressions, and jest takes a file path or -t name pattern. Go test uses -run TestName and cargo test takes a test name filter.

When should I run the full test suite instead of targeted tests?

Run the full suite only when the user explicitly requests it, when a large refactoring or dependency change makes impact scoping impossible, or when a workflow contract requires one full run before committing or merging.

Why avoid running all project tests on every change?

Full suites often take over ten minutes and can fail from local resource noise like OOM errors unrelated to your change. Narrowing scope shortens feedback loops and makes failure root causes easier to isolate.

What counts as completion for a targeted test run?

A run is complete only when the exact command and its raw output, including exit code and the pass/fail summary line, are presented in the response. Without that evidence the task is considered unfinished.