test-validator
Skill22 starsChanged 9 days agoMITView on GitHub
Run the test suite and return failures as agent-readable JSON. Use after modifying code, before declaring done, or on "run tests", "check tests", "did anything break". Not a replacement for `pnpm check`.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- joris887/exosuittheir own version, first seen Aug 20, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- joris887/exosuit★ 9same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- dependency-analyzerSkill
- docsSkill
- handoffSkill
- openai-reviewerSkill
- plugin-homeSkill
- schema-validatorSkill
- security-auditSkill
- session-auditSkill
- claude-codeSkill
- codexSkill
- opencodeSkill
- chartsSkill
- export-csvSkill
- export-excelSkill
- make-chartSkill
- make-html-reportSkill
- make-pdfSkill
- a2a-communicateSkill
- a2a-handle-inboundSkill
- codebase-inspectionSkill
- ethos-skill-authoringSkill
- native-mcpSkill
- github-authSkill
- github-code-reviewSkill
- github-issuesSkill
- github-pr-workflowSkill
- github-repo-managementSkill
- birth-ritualSkill
- get-to-know-youSkill
- xurlSkill
- arxivSkill
- grounded-citationsSkill
- research-paper-writingSkill
- reddit-researchSkill
- code-reviewSkill
- coding-agentSkill
- planSkill
- requesting-code-reviewSkill
- spikeSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- tddSkill
- writing-plansSkill
- no-ai-slopSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
No argument: runs the full test suite (pnpm test)
- Distinctive: line 42
After writing or modifying any code, before declaring done.
- Distinctive: line 43
When the user says "run tests", "check tests", "did anything break".
- Very specific: line 44
Before invoking /openai-reviewer — reviews are cleaner when tests pass first.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Test Validator
Runs vitest with the JSON reporter and parses results into a flat agent-readable shape. Avoids the parsing cost of colored console output and gives a single structured object you can act on directly.
Usage
.agents/skills/test-validator/scripts/test-validate [test-path-or-pattern]- No argument: runs the full test suite (
pnpm test) - With argument: runs only matching tests (
pnpm test <pattern>)
Output shape
{
"passed": 142,
"failed": 2,
"duration_ms": 8341,
"failures": [
{
"file": "packages/core/src/__tests__/agent-loop.test.ts",
"test": "AgentLoop > emits tool_end on rejection",
"line": 217,
"error": "expected 'tool_end' but got 'tool_start'"
}
]
}On parser failure (vitest reporter format change, no output, etc.) the script falls back to { error, raw_output } so the agent always gets something actionable.
When to use
- After writing or modifying any code, before declaring done.
- When the user says "run tests", "check tests", "did anything break".
- Before invoking
/openai-reviewer— reviews are cleaner when tests pass first. - Iterating on a single failing file: pass the file path as the argument to scope the run.
When NOT to use
- For typecheck-only or lint-only checks — call
pnpm typecheck/pnpm lintdirectly. - For the full pre-ship gate — use
pnpm check(typecheck + lint + test together). - As a synonym for "did this PR break anything" — that's
/openai-reviewerterritory.
Read-only
Runs the test suite in non-mutating mode. Does not write to the codebase. Safe to call repeatedly.
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
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.

