fix-all-tests

Executes the test suite and spawns parallel subagents to fix failing test files.

1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/luigiinred/dotfiles --skill fix-all-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-all-tests
Source: https://github.com/luigiinred/dotfiles/tree/main/dot_cursor/skills/fix-all-tests
Command: npx skills add https://github.com/luigiinred/dotfiles --skill fix-all-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automatically fixes all failing tests in a project, ensuring code integrity and saving developers significant time on manual debugging.

Core Features & Use Cases

  • Automated Test Suite Execution: Runs the full test suite to identify all failing tests.
  • Parallel Subagent Execution: Spawns multiple agents to fix individual failing test files concurrently.
  • Use Case: When a CI/CD pipeline fails due to broken tests, this Skill can be invoked to automatically resolve the issues, allowing for faster iteration cycles.

Quick Start

Use the fix-all-tests skill to fix all failing tests in the current project.

Frequently Asked Questions about fix-all-tests

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

FAQPage Schema
How do I automatically fix failing tests in my CI/CD pipeline?

Automated test fixing works by executing the test suite, parsing the output to identify failed test files, and spawning parallel subagents to correct each file individually, updating expectations to match current behavior.

Can I use automated test fixing if my implementation code is incorrect?

Automated test fixing is not suitable for incorrect implementation code, as it assumes implementation code is correct and focuses solely on updating test expectations to match current behavior.

What is the best way to fix multiple broken test files concurrently?

The best way to fix multiple broken test files concurrently is by spawning parallel subagents for each identified failing test file, allowing simultaneous corrections to update test expectations to match current behavior.

Does parallel test fixing work without configuring dependencies?

Parallel test fixing works without configuring external dependencies, utilizing a built-in Task tool for subagent execution to parse test output and correct failing test files automatically.

Why does automated test fixing update test expectations instead of debugging code?

Automated test fixing updates test expectations instead of debugging code because it assumes the implementation is correct, focusing solely on aligning test suite outputs with current application behavior.