test-fixer

Classify failing tests as code bugs or test issues across Playwright, Vitest, and Jest.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/drdanmaggs/rocket-fuel --skill test-fixer-drdanmaggs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-fixer
Source: https://github.com/drdanmaggs/rocket-fuel/tree/main/internal/plugin/skills/test-fixer
Command: npx skills add https://github.com/drdanmaggs/rocket-fuel --skill test-fixer-drdanmaggs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Test Fixer helps engineers quickly determine whether a failing test reflects a real bug or a flaky/test-setup issue, and provides guided workflows to triage, diagnose, and fix tests across Playwright, Vitest, Jest, Testing Library, and related tooling.

Core Features & Use Cases

  • Intelligent triage to classify failures as bug in code vs test issue vs framework gotcha.
  • Memory-backed pattern repository to surface known root causes and fixes.
  • Context7 guidance for framework-specific behavior when needed.
  • Automated references consultation and pattern search across docs and memory.
  • Stepwise workflows including memory updates, unskip verification, and /ship gating.

Quick Start

Provide the failing test file and error output to begin the triage workflow.

Frequently Asked Questions about test-fixer

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

FAQPage Schema
How do I determine if a failing test is a real bug or a flaky test issue?

To determine if a failing test is a bug or a flaky test issue, you can use an intelligent triage workflow. It classifies failures by leveraging a memory-backed pattern repository to surface known root causes and applies standardized fix templates.

Does test triage work with Playwright and Vitest frameworks?

Yes, test triage works with Playwright, Vitest, Jest, and Testing Library. It provides framework-specific guidance and searches known patterns across docs and memory to diagnose failures accurately within these environments.

How do I fix flaky tests using known failure patterns?

To fix flaky tests using known failure patterns, the tool searches a memory-backed repository of past root causes. It then applies standardized fix templates and records the new results to memory for future reference.

What is the best way to diagnose failing tests across different frameworks?

The best way to diagnose failing tests across different frameworks is through a stepwise triage workflow. It identifies whether the failure is a code bug or test setup issue, searches related patterns, and applies standardized fixes.

Why does my test framework keep flagging the same test failures?

Your test framework might keep flagging the same failures due to unrecognized framework gotchas or test setup issues. Recording results to a memory repository helps surface these known root causes and apply standardized fix templates automatically.