test-fixing

To systematically fix failing tests after a refactor, run `make test` to identify failures, group the errors by type and module, and apply fixes starting with infrastructure issues before moving to logic. This grouping strategy isolates root causes like import errors or signature changes for efficient resolution.

The best way to group and resolve multiple test failures is to execute `make test` and categorize the resulting errors by type, module, or root cause. This smart error grouping allows you to prioritize fixes and verify each error group systematically before proceeding to the next.

Yes, you can automate debugging test suites failing due to signature changes by running `make test` to detect the failures. The Skill analyzes the failure patterns, groups them by root cause, and guides a step-by-step fixing process with focused verification for each group.

No specific CI/CD pipeline configuration is required. The process relies on running the `make test` command locally or in an environment to identify failing tests, analyze failure patterns, and systematically apply fixes without strict pipeline dependencies.

To verify test fixes without triggering unrelated failures, the process applies focused verification after fixing each error group. By grouping similar failures by type and module first, you isolate the testing scope and confirm the specific fix is effective before moving to the next group.