test-fixing

Group failing test errors by root cause and guide targeted fixes.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/bouwerp/agentic-framework --skill test-fixing-bouwerp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-fixing
Source: https://github.com/bouwerp/agentic-framework/tree/main/skills/test-fixing
Command: npx skills add https://github.com/bouwerp/agentic-framework --skill test-fixing-bouwerp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Large test suites often produce noisy, interleaved failures that are hard to diagnose. This Skill provides a structured approach to identify failing tests, group errors by root cause, and guide minimal, verifiable fixes to restore passing results.

Core Features & Use Cases

  • Smart error grouping by error type, file/module, and root cause to prioritize fixes.
  • Deterministic workflow with isolated edits, stepwise validation, and rollback safety.
  • Cross-framework compatibility with common tools like pytest, npm test, Go test, and others.
  • Use Case: A developer runs a failing suite, the skill surfaces the dominant failure cluster and suggests targeted edits to fix the underlying issue.

Quick Start

Run the test suite and let the tool group failures and guide targeted fixes iteratively.

Frequently Asked Questions about test-fixing

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

FAQPage Schema
How do I fix failing tests grouped by root cause in a large test suite?

To fix failing tests, this skill groups noisy interleaved errors by root cause, file, and module to prioritize targeted code changes. It applies minimal edits and runs focused test subsets to verify the fixes while preserving existing functionality.

How do I debug failing pytest or npm test suites with interleaved errors?

Debug failing pytest or npm test suites by letting the skill automatically group interleaved errors by error type. It then guides isolated code edits and stepwise validation to restore passing results across different test frameworks.

Can I use this test-fixing workflow for unit, integration, and end-to-end failure scenarios?

Yes, you can use this workflow for unit, integration, and end-to-end failure scenarios. It handles failures across languages and test frameworks, detecting root causes and applying deterministic rollback if needed to ensure safe recovery.

What is the best way to systematically debug a failing test suite without breaking existing functionality?

The best way to systematically debug a failing test suite is using a deterministic workflow with isolated edits and stepwise validation. This approach detects root causes, applies minimal changes, and preserves existing functionality through rollback safety.

Why does my test suite produce noisy failures that are hard to diagnose?

Large test suites produce noisy interleaved failures that are hard to diagnose because multiple errors stem from shared root causes. This skill surfaces the dominant failure cluster and suggests targeted edits to fix the underlying issue iteratively.