Writing Tests

When to Use

• Writing or reviewing tests in any language or framework.
• Choosing what kind of test to write (unit, integration, E2E).
• Diagnosing a suite that is slow, brittle, flaky, or hard to maintain.
• Reviewing test structure, naming, or test double usage.
• Unsure what test coverage a change needs.

When NOT to use

• Auditing Python code for house-style violations outside tests: see the python skill.

Invocation Notice

• Tell the user when this skill is running: writing-tests. Skip the notice when the user asked for the skill by name or slash command; spelling and spacing need not match. A phrase from this skill's own trigger list is not a name — naming the work is not naming the skill.