Test Strategy Hardening
Diagnose or improve tests as a system, including flaky or nondeterministic suites, duplicated coverage, expensive fixtures, slow feedback, and test selection. Use only when the user explicitly makes test architecture or suite behavior the primary task. Do not trigger for ordinary implementation work, adding or fixing a regression test, resolving one product bug, or running existing checks.
Install
npx skills add swyxio/skills --skill test-strategy-hardeninggit clone --depth 1 https://github.com/swyxio/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/test-strategy-hardening ~/.claude/skills/test-strategy-hardeningPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Test Strategy Hardening Improve confidence per minute without inflating test count or ceremony. ## Counterweight: confidence, not test inventory - Start from the decision the suite must support and the plausible defect it must catch. - Search for replacement coverage before adding a test. Delete or consolidate tests when confidence remains equivalent. - Do not create unit, integration, end-to-end, snapshot, fixture, and contract layers as a completeness ladder. - Prefer fixing product nondeterminism or simplifying the seam over building elaborate test harnesses around it. - Treat coverage percentage, test count, suite breadth, and green full-suite runs as signals, not goals. - Do not refactor unrelated tests, rewrite fixtures, add retries, expand CI matrices, or run global suites solely because test code was touched. - Preserve focused failure localization; deduplication is not valuable when it makes diagnosis harder. - Stop when the named suite problem is resolved and proportionally verified. Report remaining blind spots without filling them speculatively. ## Define the contract Before changing a test suite: 1. Name the behavior that could regress and who observes it. 2. Search for existing coverage of the same invariant. 3. Choose the lowest boundary that can prove the behavior faithfully. 4. Identify time, randomness, concurrency, storage, network, global-state, and teardown dependencies.
Details
- Skill name
test-strategy-hardening- Repository
- swyxio/skills
- Path
test-strategy-hardening/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Test Strategy Hardening skill do?
Diagnose or improve tests as a system, including flaky or nondeterministic suites, duplicated coverage, expensive fixtures, slow feedback, and test selection. Use only when the user explicitly makes test architecture or suite behavior the primary task. Do not trigger for ordinary implementation work, adding or fixing a regression test, resolving one product bug, or running existing checks.
How do I install the Test Strategy Hardening skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add swyxio/skills --skill test-strategy-hardening. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Test Strategy Hardening popular?
It lives in swyxio/skills, which has 201 GitHub stars and 12 forks.
Related skills
Accelevents API
201swyxio/skills
Use when reading or updating AI Engineer Europe speaker records through the Accelevents REST API, especially for full-record PUT updates, auth header quirks, and preserving existing speaker fields.
Accelevents Speaker Sync
201swyxio/skills
Use when website speaker, session, schedule, room, track, or headshot changes must be synchronized back to Accelevents for AI Engineer Europe 2026.
Agents SDK
201swyxio/skills
Build or debug stateful applications that specifically use Cloudflare's `agents` package, including Agent classes, routing, callable methods, synchronized state, scheduling, AIChatAgent, durable execution, or Agents SDK client hooks. Do not trigger for generic AI-agent design, the OpenAI Agents SDK, or ordinary Durable Object work that does not use the Cloudflare Agents SDK.
Testing Schedule Preview
201swyxio/skills
Use when testing the AI Engineer Europe internal Bun schedule preview or public schedule page, including tooltip, modal, CFP metadata, and local preview workflows.
TDD
228pproenca/dot-skills
Test-Driven Development methodology and red-green-refactor workflow (formerly test-tdd). This skill should be used when practicing TDD, writing tests first, designing tests before implementation, or reviewing test-first approaches. Triggers on "write tests first", "test before code", "red green refactor", "test driven development". This skill does NOT cover Vitest framework specifics (use vitest skill) or API mocking with MSW (use msw skill).
Vitest
228pproenca/dot-skills
Vitest testing framework patterns for test setup, async testing, mocking with vi.*, snapshots, and test performance (formerly test-vitest). This skill should be used when writing or debugging Vitest tests. This skill does NOT cover TDD methodology (use test-tdd skill), API mocking with MSW (use test-msw skill), or Jest-specific APIs.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.