write-tests
Installation
SKILL.md
Write Tests
Use this skill to decide which automated tests are worth creating or retaining, then write or update them. It is language- and framework-agnostic; adapt its principles to the project's installed test stack. Use the target repository's terminology, requirements, fixtures, commands, and validation workflow.
Philosophy
Tests verify behavior through public interfaces, not implementation details. A good test tells you what the system does, not how it does it. Bad tests are coupled to internal structure and break on refactors that don't change behavior.
Decide Whether a Test Is Warranted
Before creating a test, ask:
What meaningful failure would this test catch, through a supported interface, against an expectation established independently of the implementation?