How do I install the Test skill?

Run npx skillmds@latest add skinnyandbald/test 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.

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?

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.

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

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

Test by skinnyandbald — Agent Skill

Name: Test
Rating: 4.5 (4 reviews)
Author: skinnyandbald

Test

Auto-detects your test framework, runs the full suite, diagnoses failures, and fixes them. Use after making code changes to verify tests pass, or when you encounter test failures you want diagnosed and fixed automatically.

File contents

Run Tests and Fix Failures

Detect test framework, run tests, diagnose and fix failures automatically.

Instructions

Step 1: Detect Test Framework

Check for test configuration files in this order:

File	Framework	Run Command
`vitest.config.` or `vite.config.` with test	Vitest	`npx vitest run`
`jest.config.*` or `package.json` jest key	Jest	`npx jest`
`phpunit.xml`	PHPUnit	`./vendor/bin/phpunit`
`pest.php` or Pest in composer.json	Pest	`./vendor/bin/pest`
`pytest.ini` / `pyproject.toml` [tool.pytest]	pytest	`pytest`
`go.mod` with `_test.go` files	Go	`go test ./...`
`Cargo.toml`	Rust	`cargo test`
`Gemfile` with rspec	RSpec	`bundle exec rspec`

Also check package.json scripts for test, test:run, test:unit, test:integration.

If CLAUDE.md specifies test commands, use those instead.

Step 2: Run Tests

Run the detected test command with run_in_background=true. Use verbose output flags where available.

Step 3: Analyze Results

If all tests pass, report the summary and stop.

If tests fail, for each failure:

Read the failing test to understand what it expects
Read the source code being tested
Classify the failure:
- Test is wrong — test expectations don't match intended behavior (update test)
- Source is wrong — code has a bug (fix source)
- Both need updating — behavior changed intentionally (update both)
- Environment issue — missing dependency, stale cache, wrong config (fix setup)

Step 4: Fix and Re-run

For each failure:

Make the minimal fix
Re-run the specific failing test to verify
Move to the next failure

After all individual fixes, run the full suite once more to catch regressions.

Step 5: Report

## Test Results

**Framework:** [detected framework]
**Command:** [command used]
**Result:** X passed, Y fixed, Z remaining

### Fixed
- [test name]: [what was wrong and what was fixed]

### Still Failing (if any)
- [test name]: [diagnosis and why it couldn't be auto-fixed]

Rules

Never delete or skip a failing test without explicit user approval
Prefer fixing source over fixing tests (tests define expected behavior)
If a fix requires changing more than ~20 lines, show the proposed change and ask before applying
If the same root cause produces multiple failures, fix the root cause once

---name: testdescription: Auto-detects your test framework, runs the full suite, diagnoses failures, and fixes them. Use after making code changes to verify tests pass, or when you encounter test failures you want diagnosed and fixed automatically.---# Run Tests and Fix FailuresDetect test framework, run tests, diagnose and fix failures automatically.## Instructions### Step 1: Detect Test FrameworkCheck for test configuration files in this order:| File | Framework | Run Command ||------|-----------|-------------|| `vitest.config.*` or `vite.config.*` with test | Vitest | `npx vitest run` || `jest.config.*` or `package.json` jest key | Jest | `npx jest` || `phpunit.xml` | PHPUnit | `./vendor/bin/phpunit` || `pest.php` or Pest in composer.json | Pest | `./vendor/bin/pest` || `pytest.ini` / `pyproject.toml` [tool.pytest] | pytest | `pytest` || `go.mod` with `_test.go` files | Go | `go test ./...` || `Cargo.toml` | Rust | `cargo test` || `Gemfile` with rspec | RSpec | `bundle exec rspec` |Also check `package.json` scripts for `test`, `test:run`, `test:unit`, `test:integration`.If CLAUDE.md specifies test commands, use those instead.### Step 2: Run TestsRun the detected test command with `run_in_background=true`. Use verbose output flags where available.### Step 3: Analyze ResultsIf all tests pass, report the summary and stop.If tests fail, for each failure:1. **Read the failing test** to understand what it expects2. **Read the source code** being tested3. **Classify the failure:** - **Test is wrong** — test expectations don't match intended behavior (update test) - **Source is wrong** — code has a bug (fix source) - **Both need updating** — behavior changed intentionally (update both) - **Environment issue** — missing dependency, stale cache, wrong config (fix setup)### Step 4: Fix and Re-runFor each failure:1. Make the minimal fix2. Re-run the specific failing test to verify3. Move to the next failureAfter all individual fixes, run the full suite once more to catch regressions.### Step 5: Report```## Test Results**Framework:** [detected framework]**Command:** [command used]**Result:** X passed, Y fixed, Z remaining### Fixed- [test name]: [what was wrong and what was fixed]### Still Failing (if any)- [test name]: [diagnosis and why it couldn't be auto-fixed]```## Rules- Never delete or skip a failing test without explicit user approval- Prefer fixing source over fixing tests (tests define expected behavior)- If a fix requires changing more than ~20 lines, show the proposed change and ask before applying- If the same root cause produces multiple failures, fix the root cause once

Frequently asked questions