agentleFS
AraszArasz/ai-badger/skills/design-tests/SKILL.md

design-tests

Skill3 starsChanged 33 days agoMITView on GitHub

Use when tests have to be designed or written for a target — "write tests for X", "add coverage here", "what should I test", a new behaviour with no test yet, a bug that needs a reproduction test, a coverage gap someone wants closed, or a bare "write some tests" with nothing named. Works with a target given or none given. Not for judging tests that already exist (review-tests) and not for diagnosing one already-flaky failure (dotnet-flaky-test-diagnosis).

The file

Files
SKILL.md

This is the generic copy. If this project has been scaffolded, prefer the unprefixed design-tests skill: it is .ai-badger/skills/design-tests/SKILL.md, and it has this project's extensions and any project-local.md merged in. This copy has neither.

The full procedure is in SKILL.full.md beside this file, unchanged — read it if the project has no .ai-badger/, or run welcome-ai-badger to scaffold one.

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.