run-all-tests-and-fix
Skill0 starsChanged 9 months agoMITView on GitHub
Execute the full test suite and systematically fix any failures, ensuring code quality and f...; keywords: test, fix. Use only on explicit request; skip in routine implementation discussions.
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Check both unit and integration tests
- Distinctive: line 22
Check if failures are related to recent changes
- Distinctive: line 24
Start with the most critical failures
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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.
Files
Run All Tests and Fix Failures
Overview
Execute the full test suite and systematically fix any failures, ensuring code quality and functionality.
Steps
- Run test suite
- Execute all tests in the project
- Capture output and identify failures
- Check both unit and integration tests
- Analyze failures
- Categorize by type: flaky, broken, new failures
- Prioritize fixes based on impact
- Check if failures are related to recent changes
- Fix issues systematically
- Start with the most critical failures
- Fix one issue at a time
- Re-run tests after each fix
Test Recovery Checklist
- Full test suite executed
- Failures categorized and tracked
- Root causes resolved
- Tests re-run with passing results
- Follow-up improvements noted
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- emaraschio/cursor-commands★ 960% same
Wrote their own version · 0
None found.
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 repository31 other files it gives its agents.
- accessibility-auditSkill
- add-documentationSkill
- add-error-handlingSkill
- address-github-pr-commentsSkill
- clarify-taskSkill
- code-reviewSkill
- create-prSkill
- database-migrationSkill
- debug-issueSkill
- deslopSkill
- diagramsSkill
- docker-logsSkill
- fix-compile-errorsSkill
- fix-git-issuesSkill
- generate-api-docsSkill
- generate-pr-descriptionSkill
- git-commitSkill
- git-pushSkill
- light-review-existing-diffsSkill
- lint-fixSkill
- lint-suiteSkill
- onboard-new-developerSkill
- optimize-performanceSkill
- overviewSkill
- refactor-codeSkill
- roadmapSkill
- security-auditSkill
- security-reviewSkill
- setup-new-featureSkill
- visualizeSkill
- write-unit-testsSkill
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.