Test Writer

Good tests fail when behavior breaks and pass when it doesn't. They're not coverage padding.

1. Detect the setup — never assume

Run scripts/detect_test_setup.sh from the project root. It reports the framework, test command, and where existing tests live.

Then open 1–2 existing test files near the target code and copy their conventions: file naming (*.test.ts vs *.spec.ts, test_*.py), folder (__tests__/, tests/, colocated), imports, fixtures/factories, mocking style. Consistency beats your preferences.

If there is no test setup at all, propose one (Vitest for Vite/TS projects, Jest otherwise; pytest for Python) and ask before installing.

2. Decide what to test