test-fixing
Systematically identify and fix all failing tests using smart grouping strategies. Use when explicitly asks to fix tests (\"fix these tests\", \"make tests pass\"), reports test failures (\"tests are failing\", \"test suite is broken\"), or completes implementation and wants tests passing.
Best for Development teams with fail…Works with GitHubLow risk
⌘source
- author
@sickn33- language
- Python
★34kstars
5.6kforks
Apr 18, 2026
✦overview.md
Key Features
- ·Systematically identifies and fixes all failing tests
- ·Uses smart grouping strategies to prioritize fixes
- ·Analyzes error types, patterns, and affected modules
- ·Prioritizes fixes by impact and dependency order
- ·Provides a step-by-step systematic approach
Use Cases
- →When a developer explicitly requests to fix failing tests
- →When test failures are reported during development
- →After completing implementation to ensure all tests pass
- →When CI/CD pipelines fail due to test failures
Best for
- ✓Development teams with failing test suites
- ✓CI/CD pipeline maintenance
- ✓Post-implementation testing verification
Not ideal for
- !One-off test creation
- !Test optimization or performance tuning
FAQs
name
test-fixing
description
Systematically identify and fix all failing tests using smart grouping strategies. Use when explicitly asks to fix tests ("fix these tests", "make tests pass"), reports test failures ("tests are failing", "test suite is broken"), or completes implementation and wants tests passing.
risk:safe
source:community
date_added:2026-02-27
Test Fixing
Systematically identify and fix all failing tests using smart grouping strategies.
When to Use
- Explicitly asks to fix tests ("fix these tests", "make tests pass")
- Reports test failures ("tests are failing", "test suite is broken")
- Completes implementation and wants tests passing
- Mentions CI/CD failures due to tests
Systematic Approach
1. Initial Test Run
Run make test to identify all failing tests.
Analyze output for:
- Total number of failures
- Error types and patterns
- Affected modules/files
2. Smart Error Grouping
Group similar failures by:
- Error type: ImportError, AttributeError, AssertionError, etc.
- Module/file: Same file causing multiple test failure
- Root cause: Missing dependencies, API changes, refactoring impacts
Prioritize groups by:
- Number of affected tests (highest impact first)
- Dependency order (fix infrastructure before functionality)
3. Systematic Fixing Process
For each group (starting with highest impact):
-
Identify root cause
- Read relevant code
- Check recent changes with
git diff - Understand the error pattern
-
Implement fix
$install
1-click copynpx skills add sickn33/antigravity-awesome-skills --skill test-fixingSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
5/ 5
excellentVery clear and well structured, with almost no room for misunderstanding.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
5/ 5
very highHighly actionable with clear, concrete steps that an agent can follow directly.