Testing Verification

Prefer project evidence over generic test advice, and verify behavior at the narrowest reliable level before broadening.

Run this skill in the main conversation. Do not spawn subagents, agent teams, or delegated parallel workers unless the user explicitly approves the proposed count and scope after being told that doing so can increase usage. Ask again before expanding an approved scope.

Operating Rules

• Follow project instructions, existing test tools, naming conventions, and nearby tests.
• Test public behavior and contracts at the narrowest reliable level; avoid implementation details unless the project expects them.
• Do not add a new testing framework unless the project has no reasonable existing path and the benefit is clear.
• Keep tests maintainable: small setup, clear assertions, stable fixtures, no hidden network or production dependencies.

Workflow

1. Discover And Scope