agentleFS
fullymiddleagedfullymiddleaged/Clawness/skills/test/SKILL.md

test

Skill5 starsChanged 4 months agoMITView on GitHub

Generate comprehensive tests for a file or module. Reads existing test patterns and matches the project's style. Covers happy paths, edge cases, error conditions, and boundary values.

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

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

  • 0

    Common

    Most of the 154 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:

    Read existing tests to match the project's style

    line 20
  2. Distinctive:

    Write the test file(s)

    line 22
  3. Distinctive:

    Run them and fix any test-level issues

    line 23

“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 Generation

Generate tests using the Clawness test-writer agent.

Steps

  1. Target — If $ARGUMENTS specifies a file or function, test that. Otherwise, find recently changed files without corresponding tests.
  2. Delegate to test-writer — Send the target code to the test-writer sub-agent. It will:
    • Read existing tests to match the project's style
    • Plan test cases covering happy path, edge cases, errors, boundaries
    • Write the test file(s)
    • Run them and fix any test-level issues
  3. Report — Show what was tested, any bugs discovered by the tests, and the test file location.

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.