Auditing Tests

When To Use

Use this skill in one of three modes that share one value bar:

• Authoring: gate every new or changed test before it lands.
• Audit: sweep one area for tests that re-assert source, duplicate stronger proof, couple to implementation, or keep test-only production seams alive. Optimize for confidence, not deletion count; continue broad audits as separate coherent follow-up PRs.
• Campaign: prune one package's or subsystem's whole test surface. Read campaign.md before starting one.

Read AGENTS.md, any scoped AGENTS.md, and the contribution guide's Unit Testing section first. This skill maintains the detailed criteria for whether a test earns its cost; isaaclab-following-coding-style covers how it is written.

Workflow

Authoring gate

Before adding a test, answer four questions. A missing answer means do not add it yet: