fix-tests

Diagnose and fix failing integration tests from saved test output files.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/threadedstack/threadedstack --skill fix-tests-threadedstack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-tests
Source: https://github.com/threadedstack/threadedstack/tree/main/.claude/skills/fix-tests
Command: npx skills add https://github.com/threadedstack/threadedstack --skill fix-tests-threadedstack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Re-running slow integration test suites just to see failure output wastes time. This Skill reads pre-saved test failure output from .temp/tests-output.txt, identifies root causes, and fixes either the application code or outdated tests without re-running the suite. ## Core Features & Use Cases - Failure Parsing: Extracts failing test files, test names, assertions, and line numbers from saved output, including detection of cascading failures from shared setup errors. - Root Cause Investigation: Compares test expectations against current implementation to determine whether the application code has a bug or the test is outdated, following a strict "no fixes without proven root cause" rule. - Targeted Fixes: Updates outdated test expectations or fixes application bugs, then runs type checks (pnpm types) on affected repos before reporting. - Use Case: You paste failing integration test output into .temp/tests-output.txt and ask the AI to fix the tests. It reads the file, traces each failure back to the source code, proves the root cause, and applies the correct fix. ## Quick Start Fix the failing integration tests using the output saved in .temp/tests-output.txt.

Frequently Asked Questions about fix-tests

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

FAQPage Schema
How do I fix failing integration tests without re-running them?▼

Paste the test failure output into .temp/tests-output.txt in your project root, then invoke the Skill. It parses the saved output to identify failing tests, assertions, and line numbers, then investigates and fixes root causes directly.

How to tell if a test failure is a bug or an outdated test?▼

Read the failing test's assertions and compare them against the current implementation code. If the expectation is correct but the code doesn't satisfy it, fix the application code; if the code changed legitimately, update the test to match.

Why do all tests in a suite fail with the same error?▼

This indicates a cascading failure from a shared setup failure, often shown by setupFailed guard patterns. Focus on fixing the first test's setup failure rather than each individual test assertion, since subsequent failures are symptoms.

Can this Skill run the integration tests for me?▼

No, it never re-runs integration tests. You run tests manually and paste the output into .temp/tests-output.txt; the Skill works only from that saved output and reminds you to re-run tests to verify fixes.

What happens if the test output file is missing or empty?▼

The Skill stops and tells you no test output was found at .temp/tests-output.txt, instructing you to run your tests and paste the failure output into that file before trying again.