testing-guidelines
Skill67 starsChanged 6 months agoApache-2.0View on GitHub
Use this skill when you are writing tests, refactoring test, or asked to run tests. This skill provides you with guidelines for testing the project.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- RootCX/RootCXtheir own version, first seen Sep 18, 2026
- PANYUXIN6/pyx-skillstheir own version, first seen Aug 12, 2026
- getsentry/sentry-mcptheir own version, first seen Mar 12, 2026
- getsentry/toolkittheir own version, first seen Mar 12, 2026
- getsentry/wardentheir own version, first seen Feb 18, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- getsentry/sentry-mcp★ 960same name
- getsentry/toolkit★ 960same name
- getsentry/warden★ 423same name
- RootCX/RootCX★ 49same name
- PANYUXIN6/pyx-skills★ 8same 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 repository5 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
4
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
- Distinctive: line 13
Use this skill when you are writing tests, refactoring test, or asked to run tests.
- Distinctive: line 14
Use this skill to get guidelines for writing tests, refactoring tests, and running tests.
- Distinctive: line 15
Use this skill to get best practices for testing the project.
- Distinctive: line 16
Use this skill to get common pitfalls to avoid when writing tests.
“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
Testing guidelines
When to use this skill?
- Use this skill when you are writing tests, refactoring test, or asked to run tests. This skill provides you with guidelines for testing the project.
- Use this skill to get guidelines for writing tests, refactoring tests, and running tests.
- Use this skill to get best practices for testing the project.
- Use this skill to get common pitfalls to avoid when writing tests.
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.