running-tests

Detects test frameworks and runs scoped tests for changed source files.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/shawn-sandy/agentics-kit --skill running-tests-shawn-sandy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: running-tests
Source: https://github.com/shawn-sandy/agentics-kit/tree/main/kit/plugins/code-testing-agent/skills/running-tests
Command: npx skills add https://github.com/shawn-sandy/agentics-kit --skill running-tests-shawn-sandy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manually figuring out which test framework a project uses and which test files correspond to changed code is repetitive and error-prone, especially in polyglot or monorepo projects. This Skill automates framework detection, test file resolution, and scoped test execution so you get pass/fail results for only the code you changed. ## Core Features & Use Cases - Automatic Framework Detection: Identifies Jest, Vitest, Mocha, pytest, go test, cargo test, or make test from config files, with nearest-ancestor tie-breaking for monorepos. - Scoped Test Execution: Resolves the test file matching each changed source file and runs only those tests instead of the full suite. - Structured Reporting: Outputs a results table with pass/fail/error counts, surfaces stderr on failures, and advises on source files missing tests. - Use Case: After editing src/utils/parser.ts, ask to run the tests — the Skill finds parser.test.ts, detects Jest from package.json, runs npx jest on that file, and reports the results. ## Quick Start Ask the assistant to run the tests for your recently changed files and report which ones pass or fail.

Frequently Asked Questions about running-tests

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

FAQPage Schema
How do I run only the tests for files I changed?▼

The Skill resolves changed files from git diff or an explicit path, finds the matching test file for each, and runs scoped commands like npx jest <test-file> or python -m pytest <test-file>. It never runs the full suite unless the framework does not support file scoping.

How does test framework detection work in a monorepo?▼

Detection walks up the directory tree from the changed file and uses the nearest ancestor config file, such as package.json for Jest or pyproject.toml for pytest. If two configs exist at the same level, a fixed priority order applies, and ambiguous cases prompt the user.

Which test frameworks are supported?▼

Supported frameworks include Jest, Vitest, Mocha, npm test fallback, pytest, go test, cargo test, and make test. Each has a defined detection signal from config files and a corresponding run command template.

What happens when a source file has no test file?▼

Files without matching tests are marked Not found and skipped during execution. The final report includes a per-language advisory suggesting the conventional test file path and directing you to the reviewing-tests skill for test content.

Why does the report show only an exit code instead of pass/fail counts?▼

Counts are extracted by scanning the last 20 lines of output for framework-specific summary patterns. If no recognizable summary is found, the Skill falls back to reporting the exit code only, with 0 meaning PASS and non-zero meaning FAIL.

Does this Skill review test quality or write new tests?▼

No, it only executes existing tests and reports results. Test quality review is handled by the reviewing-tests skill, and new test suggestions belong to the code-testing-agent plugin.