strategic-testing
Decide 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.
75
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Strategic testing
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.
- Repository
- FranciscoMoretti/chat-js
- Commit
f66626f
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.