Menu
When multiple tests fail, assign each failing test file to a separate subagent that fixes it independently in parallel.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Best practices and guidelines for optimizing the performance of Tauri applications. Use this skill when the user asks to improve the performance, reduce the bundle size, or optimize the Rust/Frontend code of a Tauri app.
Keep the Vesta Launcher architecture atlas current while changing code or docs. Use when working in /Users/eatham/Vesta/launcher on refactors, feature changes, bug fixes that reveal Module ownership, docs/tests cleanup, architecture review follow-ups, questions like "where does this area live?", or any change that creates, removes, renames, deepens, splits, or connects Modules, Interfaces, seams, Adapters, events, task flows, persisted models, resource flows, runtime preparation, launch lifecycle, or frontend state.
Perform a thorough code review focused on correctness, maintainability, performance, and best practices.
When the user repeats the same correction or convention multiple times, suggest a Cursor rule to encode it permanently.
Analyze existing code and write comprehensive unit and integration tests for it. Detects the test framework, identifies untested code paths, and generates tests with proper mocking, edge cases, and assertions. Use when the user asks to add tests, improve coverage, or test a specific module.
Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.
| name | parallel-test-fixing |
| description | When multiple tests fail, assign each failing test file to a separate subagent that fixes it independently in parallel. |
| user-invocable | true |
Speed up fixing a broken test suite by distributing failing tests across parallel subagents.
npm test -- --no-coverage 2>&1 || true
Capture the output and extract all failing test files.
Parse the test output for failing files:
FAIL src/components/Button.test.tsxFAIL src/utils/format.test.tsFAILED tests/test_api.py::test_create_userGroup by file — each file becomes one task.
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.
As each subagent completes, collect:
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.
best-of-n-runner subagents if you want isolated worktrees for each fix attempt