test-doctor

Diagnose and fix test failures across Vitest, Jest, Playwright, and .NET Test.

1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/waynebrantley/aitools --skill test-doctor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-doctor
Source: https://github.com/waynebrantley/aitools/tree/main/plugins/ai-tools/skills/test-doctor
Command: npx skills add https://github.com/waynebrantley/aitools --skill test-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill systematically diagnoses and fixes failing tests (unit, E2E, server-side) across various frameworks, preventing broken builds and ensuring code quality.

Core Features & Use Cases

  • Automated Test Fixing: Fixes failures in Vitest, Jest, Playwright, and .NET tests.
  • Resource-Aware Parallelism: Uses system resources efficiently to run fixes in parallel without overload.
  • Framework Detection: Automatically identifies the test framework and configuration.
  • Use Case: After a large refactoring or dependency update, your test suite is red. Invoke Test Doctor to automatically identify, fix, and verify all failing tests, returning your build to a green state.

Quick Start

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

Frequently Asked Questions about test-doctor

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

FAQPage Schema
How do I fix broken tests automatically across different frameworks?

Automated test fixing systematically diagnoses and repairs failing unit, E2E, and server-side tests across Vitest, Jest, Playwright, and .NET frameworks. It uses parallel subagents with iterative verification to resolve failures and restore a green build state.

Can I use this to fix Playwright and Vitest test failures at the same time?

Yes, it supports fixing Playwright and Vitest failures simultaneously, along with Jest and .NET tests. It automatically detects the test framework and configuration, then orchestrates parallel execution with file-level isolation to repair failures efficiently.

What is the best way to fix failing tests after a large code refactoring?

The best way to fix post-refactoring test failures is to use an automated diagnostic tool that identifies broken tests, applies fixes in parallel, and iteratively verifies the results until all tests pass and the build returns to green.

How does resource-aware parallelism work when running automated test fixes?

Resource-aware parallelism works by orchestrating parallel subagents that apply test fixes without overloading system resources. It uses file-level isolation and iterative verification to ensure deterministic task completion across multiple test frameworks.

Do I need to manually configure test framework detection before fixing tests?

No, manual configuration is not needed because the system automatically identifies the test framework and its configuration. It detects frameworks like Vitest, Jest, Playwright, and .NET Test, then proceeds with diagnosis and repair.

Why are my automated test fixes not resolving all failing tests in the suite?

Unresolved test fixes may occur if the iterative verification process hits resource constraints or complex cascading failures. The system uses parallel subagents and progress tracking to minimize this, but highly interdependent failures can require manual intervention.