add-tests
Skill1 starsChanged 3 months agoMITView on GitHub
When a repo has no tests or thin coverage and the user wants a real test setup. Triggers: 'add tests', 'set up testing', 'no tests', 'test coverage'. Scaffolds the right test runner for the stack and writes first meaningful tests.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- buildomator/buildomatortheir own version, first seen Nov 4, 2026
- ypxing/coding-crewtheir own version, first seen Oct 13, 2026
- owid/owid-graphertheir own version, first seen Oct 8, 2026
- dperezcabrera/pico-skillstheir own version, first seen Jul 29, 2026
- davidmeirlevy/obvious-skillstheir own version, first seen Jul 5, 2026
- tykisgod/quick-questiontheir own version, first seen Mar 28, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- owid/owid-grapher★ 1.6ksame name
- buildomator/buildomator★ 102same name
- tykisgod/quick-question★ 12same name
- davidmeirlevy/obvious-skills★ 6same name
- dperezcabrera/pico-skills★ 4same name
- ypxing/coding-crew★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- cut-a-releaseSkill
- env-and-configSkill
- license-and-legalSkill
- lint-and-formatSkill
- one-command-runSkill
- package-for-npmSkill
- package-for-pypiSkill
- readme-that-convertsSkill
- repo-hygiene-passSkill
- security-basicsSkill
- set-up-ciSkill
- ship-checklistSkill
- ship-contextSkill
- write-a-changelogSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Read .agents/ship.md for language and existing tooling.
“Common” is measured: kept by at least 6 in 10 of the 4 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.
Files
Add Tests
Untested code is not shippable. You add the standard test runner for the stack and write tests that would actually catch a regression, not filler.
Before you start
Read .agents/ship.md for language and existing tooling.
Steps
- Pick the standard runner:
node --testor vitest for Node, pytest for Python,go test, and so on. Prefer zero or few dependencies. - Test behaviour, not lines. Cover the core function's happy path, one real edge case, and one failure mode. A test that only asserts "it does not throw" is close to useless.
- Make it one command:
npm test/pytest/make test, and it must pass locally. - Add tests that would have caught a real bug you can imagine in this code.
Done when
npm test (or the stack equivalent) runs a handful of meaningful tests and passes. Note the count in the commit. Next: wire it into CI with set-up-ci.
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
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.