test-fixing
test-fixing identifies all failing tests, groups them by error type and root cause, then fixes them in priority order. It handles infrastructure issues first (imports, dependencies), then API changes, then logic bugs. After each fix group passes, it moves to the next until the full suite succeeds.
test-fixing groups failing tests by error type and root cause, then fixes them systematically.
AI-generated summary based on this skill's SKILL.md
Install
mhattingpete/claude-skills-marketplace/test-fixing · repository language: HTML
git clone https://github.com/mhattingpete/claude-skills-marketplace
cp -r claude-skills-marketplace/engineering-workflow-plugin/skills/test-fixing ~/.claude/skills/test-fixingFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How does test-fixing fix failing tests systematically?
test-fixing identifies all failing tests, groups them by error type and root cause, then fixes them in priority order. It handles infrastructure issues first (imports, dependencies), then API changes, then logic bugs. After each fix group passes, it moves to the next until the full suite succeeds.
What should I do when tests are failing after refactor?
test-fixing repairs broken test suites after code refactoring or API changes by analyzing which tests broke and why. It prioritizes failures by module and error category, then applies targeted fixes to restore the suite systematically rather than attempting random corrections.
How can test-fixing identify and fix test failures?
test-fixing identifies and prioritizes test failures by error type and affected modules, grouping similar errors together. This grouping reveals root causes—whether infrastructure, API, or logic issues—so fixes address the underlying problem rather than symptoms, preventing cascading failures.
Can test-fixing resolve CI/CD pipeline failures from broken tests?
Yes. test-fixing resolves CI/CD pipeline failures caused by test suite breakage by systematically repairing the underlying test failures. Once grouped errors are fixed in priority order and focused test runs verify each fix, the pipeline can resume.
How does test-fixing prevent regressions after fixing tests?
test-fixing verifies test fixes and prevents regressions by running focused test suites after each fix group passes. This ensures each correction actually resolves its error category before moving to the next, catching any new breakage early.
SKILL.md
rendered from the published skill — quoted content, verbatim
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 failures - 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.
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
engineering-workflow-plugin/skills/test-fixing/SKILL.md