Install any skill in seconds. Free to start, no credit card required.
Get Started Free →microck/Testing Code
Write automated tests for features, validate functionality against acceptance criteria, and ensure code coverage.
Passed 20 of 22 test cases with the skill, and 19 of 22 without it.
2 fixed18 passed either way1 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
What code coverage percentage should our test suite aim for overall, and what should critical paths require?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends aiming for greater than 80% overall code coverage and 100% coverage on critical paths | Missed | Passed |
The instructions your model reads when the skill loads.
Test writing follows a systematic approach: determine scope, understand patterns, map to requirements, write tests, verify coverage.
Read project documentation:
docs/user-stories/US-###-*.md for acceptance criteria to testdocs/feature-spec/F-##-*.md for technical requirementsdocs/api-contracts.yaml for API specificationsChoose test types needed:
Investigate current test approach:
Use code-finder agents if unfamiliar with test structure.
Convert 3-5 acceptance criteria to specific test cases across test types:
Example mapping:
## User Story: US-101 User Login
test cases passed, vs 19 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.