code-unit-test-impl
Skill0 starsChanged 7 months agoNo licenceView on GitHub
Writes behavior-focused unit tests for existing code by analyzing source behavior, matching local test conventions, detecting the active build and coverage tooling, and iterating until the requested scope reaches its target. Use this skill when the user wants to add tests for a project, module, file, class, or method; retrofit missing tests; fill coverage gaps; or keep writing tests until coverage or build gates pass. Defaults to roughly 90% coverage unless the user sets another target or the repo already enforces a stricter threshold. Does not modify production source files or relax coverage rules. Reject low-value mock-heavy tests that only inflate coverage. Trigger on: "write tests", "add tests", "unit tests for", "test coverage", "missing tests", "retrofit tests", "cover this", "what needs testing", "get coverage to 90%".
In this repository27 other files it gives its agents.
- agentic-coding-auditor-skillSkill
- code-refactor-moduleSkill
- code-review-javaSkill
- code-review-skillSkill
- code-simplifySkill
- code-tdd-implSkill
- docs-arch-summary-createSkill
- docs-impl-guide-createSkill
- docs-writing-clearly-and-conciselySkill
- feature-createSkill
- feature-implementSkill
- fix-static-analysisSkill
- focus-chainSkill
- githubSkill
- imagegenSkill
- java-test-coverageSkill
- memory-bankSkill
- mvn-build-helpSkill
- openai-docsSkill
- plans-implementSkill
- plans-task-gap-plan-createSkill
- plugin-creatorSkill
- repo-onboardSkill
- skill-creatorSkill
- skill-installerSkill
- slack-messagingSkill
- test-java-onboardSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
26 rules. About 0 are common, 21 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈21
Distinctive · estimate
This author's own choices. Worth a look.
5
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 an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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.