agentleFS
Sign inStart free
grichagricha/dangerous-skills/skills/test-helper/SKILL.md

test-helper

Skill38 starsChanged 8 months agoMITView on GitHub

Run and analyze test results. Use when the user asks to run tests, check test coverage, or verify their changes pass.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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 provide a summary of results.

    line 10
  2. Distinctive:

    Run the test suite with verbose output

    line 15
  3. Distinctive:

    If tests fail, analyze the failures and suggest fixes

    line 16
  4. Distinctive:

    If available, highlight files with low coverage.

    line 42

≈ “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.

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

Test Helper Skill

Run the project's test suite and provide a summary of results.

Process

  1. Detect the test framework (pytest, jest, vitest, go test, etc.)
  2. Run the test suite with verbose output
  3. If tests fail, analyze the failures and suggest fixes
  4. Report coverage gaps if a coverage tool is configured

Running Tests

For Python projects, run:

cd ${PROJECT_DIR} && python -m pytest -v

For Node.js projects, run:

npm test

Output Format

Test Results

Summary of pass/fail counts.

Failures

For each failure: test name, error message, and suggested fix.

Coverage

If available, highlight files with low coverage.

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