test-and-fix
Skill1 starsChanged 9 months agoApache-2.0View on GitHub
Run unit tests and automatically fix code failures, regression bugs, or test mismatches. Use when tests are failing, after implementing new features, or to repair "broken" tests.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- LucasCooperBey/claude-skillstheir own version, first seen Oct 20, 2026
- prasadmogulothu/agent-skillstheir own version, first seen Jun 28, 2026
- rayketcham-lab/qn-claude-webtheir own version, first seen Mar 30, 2026
- renatorozas/claude-code-configtheir own version, first seen Mar 19, 2026
- yu-iskw/skill-inspectorword for word, first seen Jan 23, 2026
Used with
Projects with it also use techdebt and grill.
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.
Other versions5 projects use a version of this.
Word for word · 1
- yu-iskw/skill-inspector★ 2100% same
Edited · 0
None found.
Wrote their own version · 4
- rayketcham-lab/qn-claude-web★ 2same name
- LucasCooperBey/claude-skills★ 1same name
- renatorozas/claude-code-config★ 1same name
- prasadmogulothu/agent-skills★ 0same name
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.
In this repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/tech-stack.mdcCursor rule
- build-and-fixSkill
- bumpup-versionsSkill
- clean-projectSkill
- fix-issueSkill
- improve-claude-configSkill
- initialize-projectSkill
- lint-and-fixSkill
- manage-adrSkill
- manage-changelogSkill
- node-upgradeSkill
- security-vulnerability-auditSkill
- setup-dev-envSkill
- sync-readmeSkill
- test-integration-dockerSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Identify: Run pnpm test to identify failing tests.
- Distinctive: line 21
If passed: Move to the next failing test or finish if all are resolved.
- Distinctive: line 22
If failed: Analyze the new failure (or the same one if the fix was insufficient) and repeat the loop.
- Very specific: line 26
All tests pass (as reported by pnpm test).
“Common” is measured: kept by at least 6 in 10 of the 4 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.
Files
Test and Fix Loop
Purpose
An autonomous loop for the agent to identify, analyze, and fix failing unit tests using Vitest.
Loop Logic
- Identify: Run
pnpm testto identify failing tests. - Analyze: Examine the test output to determine:
- The failing test file and line number.
- The expected vs actual values.
- Refer to ../common-references/troubleshooting.md for common test failure patterns.
- Fix: Apply the minimum necessary change to either the source code (if it's a bug) or the test code (if the test is outdated).
- Verify: Re-run
pnpm test.- If passed: Move to the next failing test or finish if all are resolved.
- If failed: Analyze the new failure (or the same one if the fix was insufficient) and repeat the loop.
Termination Criteria
- All tests pass (as reported by
pnpm test). - Reached max iteration limit (default: 5).
- The error persists after multiple distinct fix attempts, indicating a need for human intervention or a broader architectural change.
Examples
Scenario: Fixing a logic error
pnpm testfails inpackages/common/src/math.test.tsbecauseadd(2, 2)returned5.- Agent analyzes
packages/common/src/math.tsand finds a typoa + b + 1. - Agent fixes the typo to
a + b. pnpm testpasses.
Scenario: Updating a test after a deliberate change
pnpm testfails because a UI component's text changed from "Submit" to "Confirm".- Agent confirms the change was intentional.
pnpm testpasses.
Resources
- pnpm Commands for Node.js: Common commands for testing and managing dependencies.
- Testing Best Practices: Project-specific testing guidelines.
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.