Parallel Test Fixing logo

Parallel Test Fixing

Community
spencerpauly
parallel-test-fixing

When multiple tests fail, assign each failing test file to a separate subagent that fixes it independently in parallel.

Overview

Publisherspencerpauly
Repositoryawesome-cursor-skills
Skill nameparallel-test-fixing
Stars
848
Forks
169
Bundled files
Instructions only
LicenseCC0-1.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by spencerpauly on GitHub. Read the source before you install it.

Installation

Install the Parallel Test Fixing AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/parallel-test-fixing
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/spencerpauly/awesome-cursor-skills.git /tmp/awesome-cursor-skills
mkdir -p .claude/skills
cp -r /tmp/awesome-cursor-skills/resources/parallel-test-fixing .claude/skills/parallel-test-fixing
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Parallel Test Fixing in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Parallel Test Fixing on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Parallel Test Fixing is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Parallel Test Fixing

Speed up fixing a broken test suite by distributing failing tests across parallel subagents.

Workflow

1. Run the Full Test Suite

bash
npm test -- --no-coverage 2>&1 || true

Capture the output and extract all failing test files.

2. Group Failures

Parse the test output for failing files:

  • Jest: FAIL src/components/Button.test.tsx
  • Vitest: FAIL src/utils/format.test.ts
  • Pytest: FAILED tests/test_api.py::test_create_user

Group by file — each file becomes one task.

3. Launch Parallel Subagents

For each failing test file, launch a generalPurpose subagent:

Task: Fix the failing tests in <file>

The test file is: <path>
The test command is: <command to run just this file>
The error output was:
<paste the relevant failure output>

Steps:
1. Read the test file and the source file it tests
2. Understand why each test is failing
3. Fix the source code (preferred) or update the test if the test is wrong
4. Run the single test file to confirm it passes
5. Report what you changed and why

Launch all subagents simultaneously — they work in parallel since each touches different files.

4. Collect Results

As each subagent completes, collect:

  • Which tests were fixed
  • What files were changed
  • Whether the fix might conflict with another subagent's changes

5. Verify

Run the full test suite one more time to confirm everything passes:

bash
npm test

If there are new failures (from conflicting fixes), resolve them sequentially.

Tips

  • If two failing tests share the same source file, assign them to the same subagent to avoid edit conflicts
  • Set a timeout — if a subagent is stuck for 5+ minutes, check its progress
  • For large test suites (50+ failures), batch into groups of 5-10 per subagent rather than one-per-file
  • Use best-of-n-runner subagents if you want isolated worktrees for each fix attempt

Frequently asked questions

What does the Parallel Test Fixing AI skill do?

When multiple tests fail, assign each failing test file to a separate subagent that fixes it independently in parallel.

Why use Parallel Test Fixing on TypingMind?

Because you install it once and use it with any model. Parallel Test Fixing is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Parallel Test Fixing in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/parallel-test-fixing. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Parallel Test Fixing?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Parallel Test Fixing?

As many as you like. As long as a model supports skills, you can use Parallel Test Fixing with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Parallel Test Fixing AI skill free?

Yes. It is published on GitHub by spencerpauly under the CC0-1.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇