agentleFS
Sign inStart free
PMDevSolutionsPMDevSolutions/Aurelius/.claude/skills/test/SKILL.md

test

Skill9 starsChanged 19 days agoMITView on GitHub

Run the Vitest suite (React Testing Library for components): everything, one file, a name pattern, or with coverage, and report failures clearly. Use when asked to run tests or check coverage. Keywords: test, vitest, coverage, run tests

179 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-context-isolation, agentica-infrastructure and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 154 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run Vitest tests with coverage reporting.

    line 10
  2. Distinctive:

    Shows coverage report: if configured

    line 30
  3. Very specific:

    Missing setup file: Create src/test/setup.ts with import '@testing-library/jest-dom'

    line 78
  4. Very specific:

    JSX not recognized: Ensure environment: 'jsdom' in vitest config

    line 79
  5. Very specific:

    Module resolution: Check resolve.alias matches tsconfig paths

    line 80

“Common” is measured: kept by at least 6 in 10 of the 154 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Test Runner

Run Vitest tests with coverage reporting.

Purpose

This command runs the project's test suite using Vitest and React Testing Library.

Usage

/test                                   # whole suite
/test src/components/Button.test.tsx    # one file
/test -t "should render" --coverage     # by name, with coverage

With arguments, run pnpm vitest run $ARGUMENTS; without, run the whole suite.

What this command does

  1. Detects test configuration (vitest.config.ts or vite.config.ts)
  2. Runs all tests with proper configuration
  3. Shows coverage report if configured
  4. Reports failures with clear error details

Steps

1. Run all tests

pnpm vitest run

2. Run with coverage

pnpm vitest run --coverage

3. Run specific test file

pnpm vitest run src/components/Button.test.tsx

4. Run in watch mode (interactive development)

pnpm vitest

5. Run tests matching a pattern

pnpm vitest run -t "should render"

Or use the project script

./scripts/run-tests.sh

Test Types

TypeToolPatternPurpose
UnitVitest*.test.tsPure functions, utilities
ComponentVitest + RTL*.test.tsxReact component behavior
HookVitest + RTL*.test.tsCustom hook logic
E2EPlaywright*.spec.tsFull user flows
VisualStorybook*.stories.tsxComponent states

Common Issues

  • Missing setup file: Create src/test/setup.ts with import '@testing-library/jest-dom'
  • JSX not recognized: Ensure environment: 'jsdom' in vitest config
  • Module resolution: Check resolve.alias matches tsconfig paths

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free