TDD Refactor

Use this skill to make a narrow, behavior-preserving improvement. The goal is not broad cleanup; it is one concrete refactor whose value can be proven by tests and validation.

Workflow

1. Find a Small Candidate

Start by reading the repo instructions and any required docs for files likely to change. Then inspect nearby code and tests before proposing edits.

Choose a candidate only if it is:

• Small enough to finish in one pass.
• Behavior-preserving from a caller or user point of view.
• Valuable because it improves locality, reduces duplication, clarifies an interface, removes a shallow module, or makes existing behavior easier to test.
• Testable through public interfaces or stable module boundaries.

Reject candidates that require broad rewrites, new product behavior, schema/API breaks, speculative abstractions, or tests coupled to private implementation details.