testing
Skill7 starsChanged 16 days agoNo licenceView on GitHub
Design or review testing strategy, test portfolios, and test quality. Use for unit/integration/contract/E2E choices, flaky or brittle tests, mocks and test doubles, BDD review, legacy-code testing, production QA, and testing LLM or AI-generated systems. Also covers TCRDD / TCR (test && commit || revert, red-green-refactor, baby steps, commit on green, revert on failure, approval-gated TDD) and HTTP API smoke tests (smoke test, critical path test, CI gate, Hurl, .hurl files, curl smoke test).
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 171 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
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 171 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.
Other versions191 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 191
- modelcontextprotocol/servers★ 92ksame name
- lobehub/lobe-chat★ 84ksame name
- lobehub/lobehub★ 84ksame name
- penpot/penpot★ 62ksame name
- meteor/meteor★ 45ksame name
- iOfficeAI/AionUi★ 34ksame name
- garrytan/gbrain★ 31ksame name
- OpenZeppelin/openzeppelin-contracts★ 27ksame name
- tursodatabase/turso★ 25ksame name
- redis/go-redis★ 22ksame name
181 more not listed
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.
Used alongsideProjects with it also use bundle-dependency-prs, update-library-template and 8 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.
MicrosoftSkillbundle-dependency-prs
Fix broken dependency update PRs and aggregate the ones that work into one PR.
Also in 6 projects that use this
- MicrosoftSkill
update-library-template
Merges the latest Library.Template into this repo (at position of HEAD) and resolves conflicts.
Also in 6 projects that use this
zetaloopSkillassign-copilot
Assigns a GitHub issue to the Copilot coding agent, optionally specifying a custom agent. Use this when asked to assign an issue to Copilot or delegate an issue to CCA.
Also in 3 projects that use this
timmo001Skillchangeset-scope
Keep all scoped code work contained to the user-defined changeset. Use for implementation, fixes, diagnosis, refactoring, cleanup, and review when explicit instructions, named files, diffs, branches, pull requests, or injected work scopes define the boundary.
Also in 3 projects that use this
JetBrainsSkillmodule-dependencies
Add or modify IntelliJ module dependencies in `.iml` files.
Also in 3 projects that use this
CES-LtdSkilloss-pr
Use when creating a pull request, after committing changes, or when user invokes /oss-pr. Covers branch management, quality checks, commit, push, and PR creation.
Also in 3 projects that use this
In this repository53 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- documentationSkill
- fastify-best-practicesSkill
- git-heroSkill
- handoffSkill
- initSkill
- linting-neostandard-eslint9Skill
- nodejs-coreSkill
- nodeSkill
- oauthSkill
- octocatSkill
- simpleSkill
- skill-optimizerSkill
- snipgrapherSkill
- typescript-magicianSkill
- typescriptSkill
- c4-diagramSkill
- c-cppSkill
- clean-codeSkill
- code-ownershipSkill
- communicationSkill
- dantotsuSkill
- data-systemsSkill
- elixirSkill
- elmSkill
- example-mappingSkill
- explain-codeSkill
- fetch-pr-corpusSkill
- git-heroSkill
- golangSkill
- javaSkill
- kanoSkill
- lean-senseiSkill
- lisperSkill
- logging-daily-progressSkill
- markdownSkill
- mikado-methodSkill
- object-oriented-programmingSkill
- ocamlSkill
- phpSkill
- pythonSkill
- repo-docsSkill
- rescriptSkill
- rest-api-designSkill
- reviewSkill
- rubySkill
- rustSkill
- show-me-the-codeSkill
- smalltalk-pharoSkill
- the-architectSkill
- typescriptSkill
- vendor-referenceSkill
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.