adversarial-test-design
Skill0 starsChanged 4 months agoNo licenceView on GitHub
Non-obvious test-design failures where tests pass but wouldn't catch a real bug: implementation-mirroring tests, assertions too weak to fail, and missing boundary/negative cases. Use when writing or reviewing tests for correctness, right after implementation code, or when a test suite is green but confidence in it is unclear. Does not cover the red-green-refactor process itself — see test-driven-development for that.
In this repository11 other files it gives its agents.
- auth-and-web-securitySkill
- concurrency-and-consistencySkill
- docker-and-containersSkill
- find-docsSkill
- ml-pipeline-pitfallsSkill
- node-runtime-pitfallsSkill
- performance-pitfallsSkill
- react-and-nextjsSkill
- resilient-integrationsSkill
- rust-pitfallsSkill
- sql-and-migrationsSkill
The file
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.