test-guide
Skill14 starsChanged 9 months agoNo licenceView on GitHub
Guide for writing and auditing tests across all layers — unit, integration, and E2E. Use this skill when writing new tests, creating test files, deciding what to test at each layer, choosing between unit vs integration vs E2E, and also when auditing existing tests, cleaning up redundant tests, or finding missing coverage. Triggers on: "write tests", "add tests for", "create unit tests", "create integration tests", "create e2e tests", "should I test this", "what layer should this test be", "audit tests", "test cleanup", "which tests can I delete", "what tests am I missing", "review test quality".
4 other projects use a version of this.
Adopted by
Most recently taken up by
- ebibibi/claude-code-discord-bridgetheir own version, first seen Oct 9, 2026
- lablup/backend.aitheir own version, first seen Oct 8, 2026
- hong9Lee/omstheir own version, first seen Mar 1, 2026
- ebibibi/ebi-agent-chat-relaytheir own version, first seen Feb 18, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- lablup/backend.ai★ 679same name
- ebibibi/claude-code-discord-bridge★ 66same name
- ebibibi/ebi-agent-chat-relay★ 66same name
- hong9Lee/oms★ 0same 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 repository2 other files it gives its agents.
- e2e-nav-testSkill
- nextjs-bootstrapSkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 11 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
11
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 3 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.
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.