Menu

Individual skill

test-strategy-hardening

0upvotes

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.

test-strategy-hardening/SKILL.md

Read pinned source

Source commit 1acf58f08cca24b764a4352a6c30fed1f7fb9fb6

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
198
Repository last updated
Nov 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.
Back to top