agentleFS
Sign inStart free
shivae372shivae372/claude-bootstrap/.claude/skills/test-runner/SKILL.md

test-runner

Skill1 starsChanged 7 months agoApache-2.0View on GitHub

Run the project's test suite and get a structured report. Invoke when you want to run tests after making changes. Auto-activates when user says "run tests", "do tests pass", or "check if this broke anything". Routes execution to the test-runner sub-agent to keep main context clean.

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use error-handling, code-reviewer and 3 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.
  • MicrosoftSkill

    error-handling

    统一错误处理系统。在添加 API 端点、修改错误处理、添加前端 API 调用、编写错误相关测试时使用。

    Also in 3 projects that use this

  • GoogleSkill

    code-reviewer

    Also in 3 projects that use this

  • CloudflareSkill

    security-audit

    Security guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons. Use for security questions, focused reviews, vulnerability research, security audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full/comprehensive/end-to-end reviews, or requested report artifacts.

    Also in 3 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 3 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the project's test suite and return a clean pass/fail report.

    line 8
  2. Distinctive:

    Always route to the sub-agent:

    line 13
  3. Distinctive:

    Always present results as:

    line 30
  4. Distinctive:

    Never paste raw test runner output.

    line 42

“Common” is measured: kept by at least 6 in 10 of the 18 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

Purpose

Run the project's test suite and return a clean pass/fail report. Uses the test-runner sub-agent so raw test output never floods the main context.

Steps

1. Delegate to Test-Runner Agent

Always route to the sub-agent:

Use the test-runner agent to: run the full test suite and return a structured summary

2. If Quick Targeted Test Needed

For a single file or test name (low context cost, run inline):

# Jest
npx jest path/to/file.test.ts --no-coverage 2>&1 | tail -20
# Pytest  
python -m pytest tests/test_specific.py -v --tb=short 2>&1 | tail -30
# Vitest
npx vitest run src/specific.test.ts 2>&1 | tail -20

3. Report Format

Always present results as:

Tests: ✅ 42 passed | ❌ 3 failed | ⏭️ 1 skipped

Failed:
1. AuthController > expired tokens → Expected 401, got 200
2. ReviewForm > required fields → TypeError: Cannot read 'id'
3. DB > connection pool → Timeout after 5000ms

Next: [specific action to fix the first failure]

Never paste raw test runner output. Always parse and summarize.

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