test-strategy-hardening

What problem does it solve?

Many development teams maintain test suites that are flaky, duplicated, slow, or fail to cover critical product behavior, leading to false confidence, wasted debugging time, and missed regressions during refactors, releases, or production hardening work.

Core Features & Use Cases

• Test Suite Inventory & Classification: Catalog all test layers (unit, integration, e2e, visual, etc.), track pass/fail rates, flakiness, skip status, and runtime to get a full picture of your test ecosystem.
• Low-Value Test Pruning: Identify and remove duplicated, brittle, no-op, or overmocked tests that don't catch real regressions and slow down development cycles.
• High-Value Coverage Addition: Add characterization, contract, and regression tests for critical user journeys, external API boundaries, past bugs, and permission flows to catch real issues before they reach users.
• Use Case: A team preparing for a major payment processing refactor can use this skill to cut 30% of low-value tests that bloat CI runtime, and add targeted regression checks for core payment and refund flows to prevent post-refactor outages.

Quick Start

Use the test-strategy-hardening skill to audit your repository's test suite, remove low-value tests, and add high-signal regression coverage for your next major release.