test-fixing

SKILL.md

Systematically identify and fix all failing tests using smart error grouping.

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 run, error analysis, grouped fixing with verification, and final full-suite validation

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: