Can I use this with specific testing frameworks?

Yes, the skill is designed to work with standard tools like Pytest, uv, and Make, while following your project's specific conventions defined in CLAUDE.md.

How does it know what changed in the code?

The skill utilizes 'git diff' to understand recent changes, helping it identify if a failure was caused by a recent refactor, renamed function, or logic change.

Will it run my entire test suite every time?

It runs the full suite initially to map failures and at the end for final verification, but uses focused subset runs during the fixing process to save time.

Does it fix all tests at once?

No, it uses a systematic approach that fixes one prioritized group at a time, verifying each subset before moving on to the next to ensure stability.

How does the Test Fixing skill group errors?

It categorizes failures by error type (such as ImportError or AssertionError), specific module or file, and likely root cause to prioritize high-impact fixes.

Test Fixing Assistant

Name: Test Fixing Assistant
Author: mhattingpete

bymhattingpete

•

126

보안 및 테스팅

Systematically diagnoses and repairs failing test suites using smart error grouping and prioritized resolution strategies.

소개

The Test Fixing skill streamlines the debugging process by automatically categorizing test failures based on error types, modules, and root causes. Instead of tackling failures randomly, it employs a strategic 'infrastructure-first' approach—resolving import and configuration issues before moving to API changes and logic bugs. This ensures a more efficient workflow for developers dealing with refactoring regressions, CI/CD breaks, or broken test suites, ultimately reducing the time spent on manual debugging and verification.

주요 기능

Regression checking with full suite verification
Prioritized fixing strategy (Infrastructure > API > Logic)
Automated test verification for individual groups
Smart error grouping by type, module, and root cause
Integration with project-specific tools like Pytest and Make
126 GitHub stars

사용 사례

Resolving test failures after a major codebase refactor
Systematically cleaning up technical debt in large test suites
Fixing broken CI/CD pipelines caused by test regressions

소개

주요 기능

Regression checking with full suite verification
Prioritized fixing strategy (Infrastructure > API > Logic)
Automated test verification for individual groups
Smart error grouping by type, module, and root cause
Integration with project-specific tools like Pytest and Make
126 GitHub stars

사용 사례

Resolving test failures after a major codebase refactor
Systematically cleaning up technical debt in large test suites
Fixing broken CI/CD pipelines caused by test regressions