test-fixing

Group failing tests by error type and module, then iteratively fix and re-run targeted subsets.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly triages and resolves failing tests in a codebase by providing a repeatable, prioritized workflow to identify root causes, group similar errors, and verify focused fixes so developers can restore green test suites with minimal guesswork.

Core Features & Use Cases

  • Initial discovery: Run the full test suite to gather failure counts, error types, and affected modules to form a high-level map of test breakage.
  • Smart error grouping: Cluster failures by error type, module, or root cause to prioritize high-impact and dependency-blocking issues first.
  • Iterative fix-and-verify loop: Implement minimal, focused code changes, run targeted subsets of tests to confirm fixes, and progress through groups until the suite is green.
  • Use case: Ideal for developers encountering multiple failures after a refactor or for CI breakages where quick triage and rollout-safe fixes are required.

Quick Start

Run the project's test suite, group failures by type and file, and iteratively apply focused fixes while re-running targeted tests until all groups pass.

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 in a pytest suite after a refactor?▼

Fix failing tests by running the full pytest suite, grouping failures by error type and module, and iteratively applying focused code fixes to resolve root causes and eliminate regressions.

What is the best way to triage CI test breakages and resolve regressions?▼

Triage CI test breakages by running the test suite to gather failure counts, clustering similar errors by root cause, and prioritizing high-impact dependency-blocking issues for focused fixes.

How do I group test failures by error type and module to debug faster?▼

Group test failures by running the full suite to map breakage, then clustering failures by error type, module, or root cause to prioritize and resolve high-impact dependency-blocking issues first.

Can I use this approach to fix both unit and integration test suites?▼

Yes, you can fix failing unit and integration test suites in local development or CI pipelines by iteratively applying focused fixes and re-running targeted test subsets to verify resolution.

How do I verify test fixes without running the entire test suite every time?▼

Verify test fixes by implementing minimal code changes, running targeted subsets of tests to confirm the resolution, and progressing through error groups until the entire test suite is green.