fix-broken-tests

Reproduces and fixes failing pytest, Jest, and Playwright automated tests with targeted reruns and a structured report.

1|Updated Sep 6, 2024
One-click install
npx skills add https://github.com/carlos18bp/gym_project --skill fix-broken-tests-carlos18bp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-broken-tests
Source: https://github.com/carlos18bp/gym_project/tree/main/.agents/skills/fix-broken-tests
Command: npx skills add https://github.com/carlos18bp/gym_project --skill fix-broken-tests-carlos18bp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fixes broken automated tests while minimizing churn, so you can quickly restore confidence without repeatedly running the full suite.

Core Features & Use Cases

  • Targeted reproduction and debugging: Re-run the exact failing test to capture the original failure and traceback, then inspect the exercised production code.
  • Minimal, correct fixes: Apply the smallest change that addresses the root cause, avoiding production changes unless the failing behavior proves production is wrong.
  • Tight regression scope: Re-run only the failing tests plus a narrow regression slice from the same file/module to prevent unrelated failures.

Quick Start

Tell your AI to fix the specific broken Azurita test by reproducing it, identifying the root cause in the relevant code path, applying the smallest correct fix, and then verifying with the failing test plus a narrow same-module regression slice.

Frequently Asked Questions about fix-broken-tests

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

FAQPage Schema
How do I fix broken pytest tests without running the full test suite?

Fix broken pytest tests by reproducing the exact failure, identifying the root cause in the exercised code, and applying the smallest correct change with targeted reruns of only the failing tests and a tight regression slice.

What is the best way to repair failing Playwright E2E tests with minimal changes?

Repair failing Playwright E2E tests with minimal changes by reproducing the failure, inspecting the relevant production code path, applying a narrow fix, and verifying with targeted reruns plus optional server reuse.

Can I use this approach to fix broken Jest or Vitest frontend unit tests?

Yes, you can fix broken Jest or Vitest-style frontend unit tests by reproducing the failure via npm, isolating the root cause, applying the minimal correct fix, and running a narrow regression slice from the same module.

Why should I run only a narrow regression slice instead of the full test suite when fixing broken tests?

Running a narrow regression slice from the same file or module instead of the full suite minimizes churn, prevents unrelated failures, and quickly restores confidence after applying a minimal fix to broken tests.