test-suite-optimizer

Identify and fix measured bottlenecks in slow test suites and CI workflows.

2|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/nodatall/primedirective --skill test-suite-optimizer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-suite-optimizer
Source: https://github.com/nodatall/primedirective/tree/main/skills/test-suite-optimizer
Command: npx skills add https://github.com/nodatall/primedirective --skill test-suite-optimizer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the wasted developer time caused by slow test suites, long CI wait times, and flaky tests that force repeated runs, all without sacrificing the confidence of your test validation.

Core Features & Use Cases

  • Report-First Audits: Identifies slow tests, expensive setup/teardown, flaky hotspots, and CI bottlenecks with measured evidence, stopping before any changes unless you explicitly approve fixes.
  • Bounded Fix Loops: Runs a structured optimization loop via /goal that implements only safe, high-impact changes with before/after validation, preserving test coverage and isolation.
  • Use Case: If your CI pipeline takes 20+ minutes to return test results, or flaky tests force you to re-run suites repeatedly, this skill pinpoints root causes and fixes them without weakening assertions or removing tests.

Quick Start

Invoke the test-suite-optimizer skill to audit your test suite for speed improvements, or run /goal test-suite-optimizer to automatically implement safe, measured optimizations that cut feedback time without losing validation confidence.

Frequently Asked Questions about test-suite-optimizer

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

FAQPage Schema
How do I fix slow test suite runtime and long CI feedback speed without losing validation confidence?

To fix slow test suite runtime safely, you need a report-first audit that identifies measured bottlenecks like expensive setup/teardown and flaky tests, then applies bounded fix loops with before/after validation to preserve coverage and isolation.

What's the best way to find and fix flaky tests that force repeated CI runs?

The best way to fix flaky tests is auditing hotspots with measured evidence to pinpoint root causes, then applying structured optimization loops that implement safe changes without weakening assertions or removing tests.

How do I optimize CI runner configurations and cache workflows for faster test results?

Optimizing CI runner configs and cache workflows requires measuring setup/teardown costs and artifact bottlenecks first, then gating risky changes for human approval before implementing high-impact fixes with before/after evidence.

Can I speed up unit, integration, and e2e test surfaces all at the same time?

Yes, you can optimize unit, integration, and e2e test surfaces simultaneously by running a structured optimization loop that targets each surface's specific bottlenecks while preserving test coverage and isolation across the board.

Does test suite optimization remove tests or weaken assertions to improve speed?

No, proper test suite optimization does not remove tests or weaken assertions; it cuts feedback time by identifying and fixing measured bottlenecks in setup/teardown and CI workflows while explicitly preserving validation confidence.

When should I require human approval before applying test suite speed improvements?

You should require human approval for test suite speed improvements whenever changes are risky or lack clear before/after evidence; safe, high-impact optimizations can proceed automatically within bounded fix loops.