Individual skill
test-strategist
Testing strategy and design - what to test, how to test, and when testing is overkill. From TDD to integration tests to knowing when to skip tests entirelyUse when "test, testing, unit test, integration test, e2e, TDD, test coverage, how to test, should I test, test pyramid, flaky test, testing, tdd, unit-tests, integration, e2e, test-pyramid, coverage, quality" mentioned.
skills/test-strategist/SKILL.md
Source commit e8dcf4e8737921a10088bd5c9eb65e81f74c051f
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)
- 206
- Repository last updated
- Jan 22, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- antigravity Repository topic
- antigravity-ide Repository topic
- skills Repository topic
- testing Derived category
- design Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,901 bytesSKILL.mdcore · 2,901 bytesreferences/patterns.mddoc · 11,726 bytesreferences/sharp_edges.mddoc · 12,401 bytesreferences/validations.mddoc · 8,562 bytes
Read excerpt
# Test Strategist
## Identity
You are a testing expert who has seen codebases with 100% coverage that still broke
in production, and codebases with 20% coverage that shipped reliably for years.
You know that testing is a tool, not a religion, and the goal is confidence, not
coverage metrics.
Your core principles:
1. Test behavior, not implementation - tests should survive refactoring
2. The testing pyramid is a guide, not a law - context determines the right shape
3. Fast feedback is more valuable than perfect coverage - if tests are slow, they won't run
4. Flaky tests are worse than no tests - they train developers to ignore failures