How do I install the Test Run skill?

Run npx skillmds@latest add laurigates/test-run in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Test Run safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Test Run?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Test Run free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Test Run?

laurigates (@laurigates) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Test Run by laurigates — Agent Skill

Name: Test Run
Rating: 4.5 (4 reviews)
Author: laurigates

File contents

When to Use This Skill

Use this skill when...	Use test-quick instead when...
Running tests with auto-detected framework (pytest, vitest, jest, cargo, go)	You only want fast unit tests for sub-30s feedback
Running a specific file or pattern with full framework defaults	Iterating on a single failing spec (use test-focus)
Generating coverage in the standard run	Running the full pyramid before a PR (use test-full)
Starting a watch-mode dev loop across the project	Triaging existing test results (use test-analyze)

Context

Project indicators: !find . -maxdepth 1 $ -name 'pyproject.toml' -o -name 'package.json' -o -name 'Cargo.toml' -o -name 'go.mod' $
Test directories: !find . -maxdepth 1 -type d $ -name 'tests' -o -name 'test' -o -name '__tests__' -o -name 'spec' $
Package.json test script: !find . -maxdepth 1 -name 'package.json' -exec grep -A2 '"test"' {} +
Pytest config: !find . -maxdepth 1 -name 'pyproject.toml' -exec grep -A5 '\[tool.pytest' {} +

Parameters

$1: Optional test pattern or specific test file/directory
--coverage: Enable coverage reporting
--watch: Run tests in watch mode

Your task

Delegate this task to the test-runner agent.

Use the Agent tool with subagent_type: testing-plugin:test-runner to run tests with the appropriate framework. Pass all the context gathered above and the parsed parameters to the agent.

The test-runner agent should:

Detect project type and test framework:
- Python: pytest, unittest, nose
- Node.js: vitest, jest, mocha
- Rust: cargo test
- Go: go test
Run appropriate test command:
- Apply test pattern if provided
- Enable coverage if requested
- Enable watch mode if requested
Analyze results:
- Parse test output for pass/fail counts
- Identify failing tests with clear error messages
- Extract coverage metrics if available

Provide concise summary:

Tests: [PASS|FAIL]
Passed: X | Failed: Y | Duration: Zs

Failures (if any):
- test_name: Brief error (file:line)

Coverage: XX% (if requested)

Suggest next actions:
- If failures: specific fix recommendations
- If coverage gaps: areas needing tests
- If slow: optimization suggestions

Provide the agent with:

All context from the section above
The parsed parameters (pattern, --coverage, --watch)
Any specific test configuration detected

The agent has expertise in:

Multi-framework test execution
Test failure analysis and debugging
Coverage reporting and gap identification
Tiered test execution (unit, integration, e2e)

---name: test-rundescription: Run the project's tests — auto-detects pytest, vitest, jest, cargo, go test; whole suite or a name pattern. Use when asked to run the tests and no tier, single file, or fix cycle is named.--- ## When to Use This Skill | Use this skill when... | Use test-quick instead when... | |---|---| | Running tests with auto-detected framework (pytest, vitest, jest, cargo, go) | You only want fast unit tests for sub-30s feedback | | Running a specific file or pattern with full framework defaults | Iterating on a single failing spec (use test-focus) | | Generating coverage in the standard run | Running the full pyramid before a PR (use test-full) | | Starting a watch-mode dev loop across the project | Triaging existing test results (use test-analyze) | ## Context - Project indicators: !`find . -maxdepth 1 $ -name 'pyproject.toml' -o -name 'package.json' -o -name 'Cargo.toml' -o -name 'go.mod' $` - Test directories: !`find . -maxdepth 1 -type d $ -name 'tests' -o -name 'test' -o -name '__tests__' -o -name 'spec' $` - Package.json test script: !`find . -maxdepth 1 -name 'package.json' -exec grep -A2 '"test"' {} +` - Pytest config: !`find . -maxdepth 1 -name 'pyproject.toml' -exec grep -A5 '\[tool.pytest' {} +` ## Parameters - `$1`: Optional test pattern or specific test file/directory - `--coverage`: Enable coverage reporting - `--watch`: Run tests in watch mode ## Your task **Delegate this task to the `test-runner` agent.** Use the Agent tool with `subagent_type: testing-plugin:test-runner` to run tests with the appropriate framework. Pass all the context gathered above and the parsed parameters to the agent. The test-runner agent should: 1. **Detect project type and test framework**: - Python: pytest, unittest, nose - Node.js: vitest, jest, mocha - Rust: cargo test - Go: go test 2. **Run appropriate test command**: - Apply test pattern if provided - Enable coverage if requested - Enable watch mode if requested 3. **Analyze results**: - Parse test output for pass/fail counts - Identify failing tests with clear error messages - Extract coverage metrics if available 4. **Provide concise summary**: ``` Tests: [PASS|FAIL] Passed: X | Failed: Y | Duration: Zs Failures (if any): - test_name: Brief error (file:line) Coverage: XX% (if requested) ``` 5. **Suggest next actions**: - If failures: specific fix recommendations - If coverage gaps: areas needing tests - If slow: optimization suggestions Provide the agent with: - All context from the section above - The parsed parameters (pattern, --coverage, --watch) - Any specific test configuration detected The agent has expertise in: - Multi-framework test execution - Test failure analysis and debugging - Coverage reporting and gap identification - Tiered test execution (unit, integration, e2e)

Frequently asked questions

Test Run