Vitest Config Validator

Validate vitest.config.ts/js and vitest workspace configurations for syntax, deprecated options, plugin conflicts, and best practices. Use when validating Vi...

Security Scan

The skill's code and instructions are consistent with a local, regex-based Vitest config linter that reads files and reports issues; it does not request credentials or install software.

Purpose & Capability

Name/description (Vitest config validator) match the provided assets: an instruction-only SKILL.md and a Python script that parses vitest.config.ts/js files. Required env vars, binaries, and config paths are not requested, which is coherent for a local validator.

Instruction Scope

SKILL.md instructs running the included Python script against local config files. The script reads the target config file(s) and applies regex-based checks; the repo explicitly states it parses text and does not execute JS. The instructions do not request unrelated system files or external endpoints.

Install Mechanism

There is no install spec — instruction-only plus an included Python script. This is low-risk and proportionate to the stated purpose. No download-from-URL or package installs are required.

Credentials

The skill requests no environment variables or credentials. The script operates on file paths supplied by the user, which is appropriate for a config linter.

Persistence & Privilege

The skill does not declare always:true and has no install-time hooks. It does not request persistent system-wide changes or elevated privileges in the provided metadata or instructions.

Assessment

This skill appears to be a local, regex-based Vitest configuration linter and is internally consistent with that purpose. Before installing/using it: (1) inspect the full Python file for any network/callout patterns (search for subprocess, os.system, socket, requests, urllib, http, fetch) to confirm there are no hidden external calls; (2) run it on sample or non-sensitive config files first and in a sandboxed environment if possible; (3) avoid passing paths to sensitive files or directories you don't intend to expose; (4) expect false positives/negatives because the tool uses heuristic/regex parsing rather than executing the config. If you want higher assurance, provide the full (untruncated) script for a line-by-line review — that could raise confidence to high.

Validate vitest.config.ts and vitest.config.js files for syntax errors, deprecated options, plugin conflicts, and best practices. Parses config files as text using regex patterns — no JS execution required.

Commands

# Full validation (all rules)
python3 scripts/vitest_config_validator.py validate vitest.config.ts

# Quick syntax-only check (structure rules only)
python3 scripts/vitest_config_validator.py check vitest.config.ts

# Explain config in human-readable form
python3 scripts/vitest_config_validator.py explain vitest.config.ts

# Suggest improvements
python3 scripts/vitest_config_validator.py suggest vitest.config.ts

# JSON output
python3 scripts/vitest_config_validator.py validate vitest.config.ts --format json

# One-line PASS/WARN/FAIL summary
python3 scripts/vitest_config_validator.py validate vitest.config.ts --format summary

# Strict mode (warnings become errors)
python3 scripts/vitest_config_validator.py validate vitest.config.ts --strict

Rules (22)

#	Category	Severity	Rule
S1	Structure	E	File not found or unreadable
S2	Structure	E	Empty config or no defineConfig call
S3	Structure	W	No default export found
S4	Structure	W	Both vitest.config and vite.config with test section detected
S5	Structure	W	Unknown top-level config keys
T1	Test Settings	E	Invalid test environment (must be jsdom/happy-dom/node/edge-runtime)
T2	Test Settings	W	Empty include or exclude patterns
T3	Test Settings	E	Invalid glob pattern in include/exclude
T4	Test Settings	I	Coverage provider not set (recommend c8/v8/istanbul)
T5	Test Settings	W	testTimeout set unreasonably high (>60000ms) or low (<100ms)
P1	Performance	W	singleThread: true used with forks pool (disables parallelism)
P2	Performance	W	isolate: false without comment (risky for test isolation)
P3	Performance	I	No pool configuration (defaults may not be optimal)
P4	Performance	W	globals: true without type declaration reference
C1	Compatibility	W	Deprecated option used
C2	Compatibility	W	css.modules without css.include (potential miss)
C3	Compatibility	W	deps.inline and deps.external conflict
B1	Best Practices	I	No reporter configured
B2	Best Practices	I	Missing coverage configuration
B3	Best Practices	W	setupFiles references potentially non-existent pattern
B4	Best Practices	I	snapshotFormat not explicitly configured
B5	Best Practices	I	passWithNoTests not set (CI may fail on empty test suite)

Output Formats

• text (default): Human-readable with [E]/[W]/[I] severity prefix
• json: Machine-readable structured output
• summary: Single-line PASS / WARN / FAIL

Exit Codes

• 0 — No errors
• 1 — Errors found (or warnings in --strict mode)
• 2 — File not found or parse error