agentleFS
codewhale-hqcodewhale-hq/codewhale-plugin-marketplace/skills/test/SKILL.md

test

Skill5 starsChanged 16 days agoMITView on GitHub

Detect the project’s test stack, run the narrowest useful tests, create tests when authorized, and report coverage/gaps honestly.

179 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-context-isolation, agentica-infrastructure and 10 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.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 154 edited versions we read keep these.

  • 5

    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:

    Use when the user wants tests run, added, or improved for a concrete surface.

    line 10
  2. Distinctive:

    Do not invent a test framework the repo does not use.

    line 13
  3. Distinctive:

    Do not claim coverage you did not measure.

    line 14
  4. Distinctive:

    Run the narrowest useful suite for the change.

    line 18
  5. Distinctive:

    Add or update tests only when authorized.

    line 19

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

When to use

Use when the user wants tests run, added, or improved for a concrete surface.

Non-goals

  • Do not invent a test framework the repo does not use.
  • Do not claim coverage you did not measure.

Workflow

  1. Detect the repo’s test runner and conventions.
  2. Run the narrowest useful suite for the change.
  3. Add or update tests only when authorized.
  4. Report pass/fail with commands and residual gaps.

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.