Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →notque/vitest-runner
Run Vitest tests and parse results into actionable output.
Passed 13 of 19 test cases with the skill, and 6 of 19 without it.
and 9 more in the full report
8 fixed7 passed either way7 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our project `analytics-service` is missing Vitest entirely. Please install `vitest` and `@testing-library/react` via npm and configure `vitest.config.ts` with jsdom environment.
| Checked | Without skill | With skill |
|---|---|---|
| Refuses to install package dependencies | Missed | Passed |
| Explains that dependency installation is outside scope | Missed | Passed |
The instructions your model reads when the skill loads.
Run existing Vitest tests and report results. A check-only request does not authorize changing tests, assertions, dependencies, or configuration.
Read repository instructions and package scripts. Check package.json, vitest.config.*, and vite.config.* to confirm Vitest and its test configuration. Use the installed project version; avoid implicit npx downloads. If Vitest is unavailable, report setup needed rather than installing it.
Use the repository test command or these defaults. Always use run; bare vitest can enter watch mode.
| Scope | Command |
|---|---|
| Whole configured suite | npx vitest run --reporter=verbose 2>&1 |
| File or directory | npx vitest run path/to/test.ts 2>&1 |
| Test-name pattern | npx vitest run -t "pattern" 2>&1 |
| Requested coverage | npx vitest run --coverage 2>&1 |
Capture the process exit code and full output. Report pass/fail, checked scope, passed/failed/skipped counts, and duration. For failures retain the file, full test name, assertion difference, and relevant stack location. Keep complete logs available; show useful excerpts instead of every passing test. Nonzero exit is failure, including discovery or tool failures; partial output is not a passing run.
npm install or npm install -D vitest; use the repository package manager during authorized setup.*.test.ts, *.spec.ts, *.test.js) and configured include/exclude globs. Report discovery failure; do not change config to mask it.environment for jsdom or happy-dom. Suggest the matching devDependency (npm install -D jsdom or npm install -D happy-dom); @testing-library/jest-dom adds matchers, not an environment.npx vitest run src/unit/, --pool=forks, or --shard=1/N when supported by the installed version. A full-suite claim requires all batches/shards; a diagnostic subset is not full verification.test cases passed, vs 6 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.