MCPInstall

parallel-test-fixing

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

Installs
416
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/spencerpauly/awesome-cursor-skills --skill parallel-test-fixing
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads parallel-test-fixing automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Parallel Test Fixing

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

Workflow

1. Run the Full Test Suite

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:

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

FAQ

What does the parallel-test-fixing skill do?

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

How do I install parallel-test-fixing?

Run npx skills add https://github.com/spencerpauly/awesome-cursor-skills --skill parallel-test-fixing in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/parallel-test-fixing/ (personal) or .claude/skills/parallel-test-fixing/ (project).

Which AI agents can use parallel-test-fixing?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is parallel-test-fixing safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains parallel-test-fixing?

It is published by spencerpauly in spencerpauly/awesome-cursor-skills. It has 416 recorded installs.

More from spencerpauly/awesome-cursor-skills

View all →

visual-qa-testing

spencerpauly/awesome-cursor-skills

Visually QA a web application by launching it in Cursor's built-in browser, taking screenshots, checking console errors, and auditing network requests. Use after making UI changes to verify they look correct.

Testing & QA648 installs

auditing-security

spencerpauly/awesome-cursor-skills

Perform a systematic security audit of a codebase, checking for OWASP Top 10 vulnerabilities, secrets exposure, and insecure patterns.

Security598 installs

responsive-testing

spencerpauly/awesome-cursor-skills

Open the app in Cursor's browser at multiple viewport sizes, screenshot each, and report any layout breakage.

Testing & QA569 installs

suggesting-cursor-rules

spencerpauly/awesome-cursor-skills

When the user repeats the same correction or convention multiple times, suggest a Cursor rule to encode it permanently.

559 installs

systematic-debugging

spencerpauly/awesome-cursor-skills

Structured debugging methodology — reproduce, isolate, hypothesize, verify. Covers git bisect, binary search, logging, and minimal reproduction.

grinding-until-pass

spencerpauly/awesome-cursor-skills

Keep iterating on code changes until the tests pass, the build succeeds, or linting is clean. Runs in a tight loop of fix → run → check → repeat. Use when you want the agent to autonomously grind through test failures or build errors.

Testing & QA551 installs

Popular testing & qa skills

View category →

tdd

mattpocock/skills

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

Testing & QA1.2M installs

grilling

mattpocock/skills

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

Testing & QA996.2K installs

migrate-to-shoehorn

mattpocock/skills

Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.

Testing & QA484.1K installs

run-train

lllllllama/rigorpilot-skills

Rigor Train skill for deep learning research repositories. Use when a documented or selected training command should be run conservatively for startup verification, short-run verification, full kickoff, or resume, with command, config, seed, log, checkpoint, status, and metric evidence written to standardized trainoutputs/. Do not use for environment setup, exploratory sweeps, speculative idea implementation, or end-to-end orchestration.

Testing & QA337.8K installs

test-driven-development

obra/superpowers

Use when implementing any feature or bugfix, before writing implementation code

Testing & QA261.8K installs

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

Testing & QA216.8K installs