agentleFS
Sign inStart free
amanning3390amanning3390/hermeshub/skills/test-runner/SKILL.md

test-runner

Skill48 starsChanged 5 months agoMITView on GitHub

Write and run tests across languages — scaffolding, execution, and coverage. Use when the user mentions tests, testing, coverage, TDD, or wants to verify code correctness.

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

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

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 3

    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 test suite

    line 32
  2. Distinctive:

    Don't test implementation details, test behavior

    line 50
  3. Distinctive:

    No flaky tests on repeated runs

    line 58

“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

Test Runner

Multi-language test scaffolding, execution, and analysis.

When to Use

  • User wants to write tests for existing code
  • User asks to run a test suite
  • User wants coverage analysis
  • User practices TDD and needs test scaffolding

Procedure

  1. Detect language and testing framework
  2. Analyze the code under test
  3. Generate test cases covering:
    • Happy path (expected behavior)
    • Edge cases (empty input, null, boundaries)
    • Error cases (invalid input, exceptions)
  4. Run the test suite
  5. Report results and coverage

Supported Frameworks

LanguageFrameworkRun Command
JavaScript/TSJestnpx jest
PythonPytestpython -m pytest
Gogo testgo test ./...
Rustcargo testcargo test

Test Patterns

  • Arrange-Act-Assert for unit tests
  • Given-When-Then for behavior tests
  • Table-driven tests for parameterized cases
  • Mock external dependencies

Pitfalls

  • Don't test implementation details, test behavior
  • Mock external services, don't hit real APIs
  • Clean up test fixtures after each test
  • Watch for flaky tests (timing, ordering)

Verification

  • All tests pass
  • Coverage meets threshold (aim for 80%+)
  • No flaky tests on repeated runs

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