test-scenario-hygiene

To clean up temporary test scaffolding after TDD, review session changes to categorize tests by long-term value versus temporary scaffolding, then remove unused cases and run formatters and linters to ensure codebase cleanliness.

The best way to remove unused test cases involves gathering session changes, delegating review to a subagent to categorize tests, presenting results, applying user decisions, and running formatters and linters for a repeatable workflow.

Test cleanup categorizes tests by reviewing session changes to distinguish temporary TDD scaffolding from tests offering long-term value, allowing developers to prune noise and apply targeted user decisions before final formatting.

Yes, you can run formatters and linters automatically after removing test scaffolding, as the cleanup workflow enforces steps to apply user decisions and execute formatting and linting to maintain a clean codebase.

Yes, test scenario hygiene works without external dependencies, operating through a self-contained workflow that gathers changes, delegates review via a subagent, and applies formatting and linting independently.

You should avoid pruning test scenarios when session changes are still incomplete or uncommitted, as the hygiene workflow targets reviewing established session changes to categorize and remove temporary TDD scaffolding safely.