Systematically identify and fix all failing tests using smart error grouping.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add sickn33/antigravity-awesome-skills --skill test-fixingCompatible with
Supported agents
Groups failures by error type, affected module, and root cause, then prioritizes fixes by impact and dependency order
Fixes infrastructure issues first (imports, dependencies, configuration), followed by API changes, then logic bugs
Runs focused test subsets after each fix using pytest markers and file patterns to verify progress before moving to the next group
Follows a structured workflow: initial test
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiontest-fixingExecute the skills CLI command in your project's root directory to begin installation:
epx add sickn33/antigravity-awesome-skills --skill test-fixingFetches test-fixing from sickn33/antigravity-awesome-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/test-fixing
Restart Cursor to activate test-fixing. Access via /test-fixingin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
backend-architect
sickn33/antigravity-awesome-skills · Backend · same repo
brainstorming
sickn33/antigravity-awesome-skills · AI/ML · same repo
react-native-architecture
sickn33/antigravity-awesome-skills · Frontend · same repo
seo-content-writer
sickn33/antigravity-awesome-skills · Marketing · same repo
frontend-slides
sickn33/antigravity-awesome-skills · Frontend · same repo
tailwind-design-system
sickn33/antigravity-awesome-skills · Frontend · same repo
I recommend test-fixing for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
test-fixing is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added test-fixing from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
test-fixing has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: test-fixing is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: test-fixing is focused, and the summary matches what you get after install.
I recommend test-fixing for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: test-fixing is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in test-fixing — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
test-fixing reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 60