Strategic testing
SkillDev toolsDecide whether a change warrants new tests and choose proportionate verification. Use before adding tests, when planning validation, or when reviewing whether a proposed test protects meaningful behavior.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Strategic testing skill
What this skill tells your AI
The instructions your AI receives, as published by franciscomoretti/chat-js in .agents/skills/strategic-testing/SKILL.md and read by ahel’s review.
Add tests only when they protect meaningful behavior or a stable contract that existing checks could realistically miss.
- Prioritize domain invariants, important edge cases, public interfaces, persisted data, security boundaries, and integration seams.
- Skip tests for mechanical edits, implementation details, existing coverage, or changes already verified by types, linting, or schema validation.
- Choose the smallest test level that protects the behavior.
Before adding a test, identify the realistic failure it prevents and confirm that the maintenance cost is justified. If that case is weak, do not add one.
Signals
- GitHub stars
- 1k
- Forks
- 122
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
strategic-testing- Source
- github.com/franciscomoretti/chat-js