refine-tests

Reviews existing test code for conformance to the test-designing-guide and test-writing-guide, then applies the refinements.

Scope Check

This skill is for refining existing tests for conformance to the guides. If the request is out of scope, redirect:

• Adding tests for a new feature or spec change → use /plan-feature instead
• A failing test, or a test that verifies incorrect behavior → use /fix-bug instead

Input

One or more file path arguments. Resolve them to the concrete set of test files to review before proceeding.

If no path argument is given, use AskUserQuestion to ask the user for the targets. Do not derive targets from git status — that would silently widen the scope beyond what was requested.

Workflow

Recording implementation notes: Notes for this run go in <scratchpad>/implementation-notes.md, where <scratchpad> is the scratchpad directory listed in your system prompt (write its absolute path literally). Immediately before your first append in this run — and only then — delete that file if it exists (usually it will not), so this run starts from an empty one: every /fix-bug, /refine-tests, and plan-file run in the session shares this file, so an earlier run abandoned before its Implementation Notes step would otherwise leak its notes into this one.

While working through Steps 5–6, whenever one of the following occurs, immediately append a line to that file — do not wait until the end to reconstruct these from memory:

• A Finding was ambiguous, or proved wrong once applied, and you made a judgment call → Design decisions
• You intentionally departed from a Finding, and why → Deviations
• You considered alternatives and chose one, and why → Tradeoffs
• You changed production code — a method demoted to private, a dead test-only seam removed, or any other production edit — and why → Production code changes

Append with Bash — the Write tool cannot append:

cat >> "<scratchpad>/implementation-notes.md" <<'EOF'
- **Production code changes**: <one line>
EOF