Install any skill in seconds. Free to start, no credit card required.
Get Started Free →dokhacgiakhoa/test-fixing
Run tests and systematically fix all failing tests using smart error grouping.
Passed 16 of 21 test cases with the skill, and 14 of 21 without it.
and 3 more in the full report
5 fixed13 passed either way3 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
We modified our Go backend interfaces and now 'go test ./...' fails with 12 errors in pkg/auth and pkg/storage. Should we edit all failing test files at once and run the full suite at the end, or what step-by-step methodology should we follow? Describe the process.
| Checked | Without skill | With skill |
|---|---|---|
| Groups errors by interface signature mismatch before editing code. | Missed | Passed |
| Recommends running targeted package tests after fixing each error group. | Missed | Passed |
The instructions your model reads when the skill loads.
Systematically identify and fix all failing tests using smart grouping strategies.
test cases passed, vs 14 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.