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.
Profile →npx skills add sickn33/agentic-awesome-skills --skill test-fixing --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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): 1. **Identify root cause** - Read relevant code - Check recent changes with `git diff` - Understand the error pattern 2. **Implement fix** - Use Edit tool for code changes - Follow project conventi
- When to Use
- Systematic Approach
- 1. Initial Test Run
- 2. Smart Error Grouping
- 3. Systematic Fixing Process
- 4. Fix Order Strategy
- 5. Final Verification
- Best Practices
- Example Workflow
- Limitations
uv run pytest tests/path/to/test_file.py -v uv run pytest -k "pattern" -v
What does the test-fixing skill do?
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.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill test-fixing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.