test-fixing

Diagnose and fix failing tests by grouping errors and applying targeted fixes.

Updated Aug 12, 2026
One-click install
npx skills add https://github.com/Barbaros911/As-mine --skill test-fixing-barbaros911
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-fixing
Source: https://github.com/Barbaros911/As-mine/tree/main/.claude/skills/test-fixing
Command: npx skills add https://github.com/Barbaros911/As-mine --skill test-fixing-barbaros911

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a test suite breaks after a refactor or dependency change, developers face dozens of scattered failures with no clear starting point. This Skill turns that chaos into an ordered plan by grouping failures by root cause and fixing them systematically. ## Core Features & Use Cases - Smart Error Grouping: Clusters failures by error type (ImportError, AttributeError, AssertionError), affected module, and root cause so related issues are fixed together. - Prioritized Fix Order: Resolves infrastructure problems first (imports, dependencies, configuration), then API changes, then logic bugs, maximizing impact per fix. - Incremental Verification: Runs focused test subsets after each fix group before re-running the full suite to confirm no regressions. - Use Case: After renaming a module, your suite reports 15 failures. The Skill groups them into 8 import errors, 5 signature mismatches, and 2 logic bugs, fixes each group in order, and verifies the full suite passes. ## Quick Start Ask the assistant to run the test suite and systematically fix all failing tests by grouping similar errors together.

Frequently Asked Questions about test-fixing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix multiple failing tests after a refactor?▼

Run the full test suite first, then group failures by error type such as ImportError or AttributeError. Fix infrastructure issues like renamed modules before logic bugs, and verify each group with focused test runs before moving on.

How to run only a subset of pytest tests?▼

Use pytest with a file path or the -k flag to filter tests by name pattern, for example pytest tests/path/to/test_file.py -v or pytest -k "pattern" -v. This lets you verify one fix group without running the entire suite.

What order should I fix test failures in?▼

Fix import errors, missing dependencies, and configuration issues first, then API changes like renamed functions or changed signatures, and finally assertion failures and logic bugs. Infrastructure fixes often resolve many downstream failures at once.

Why do tests fail after renaming a module or function?▼

Renames break import statements and call sites that still reference the old name, producing ImportError or AttributeError failures. Use git diff to identify recent changes and update all references consistently.

When should I not group test fixes together?▼

Avoid grouping when failures have unrelated root causes, since a fix for one may mask or conflict with another. Verify each group passes independently before proceeding to the next.