Refactor code with safety nets
refactorskillsetup L1★594
poshan0126/dotclaude ↗What it does
Safely refactor code with test coverage as safety net
Best for
Large refactoring efforts where test coverage provides a safety net to avoid breaking changes.
Inputs
- · Target code/function/pattern to refactor
- · Existing test suite
Outputs
- · Refactored code with same external API
- · All tests passing
Requires
- · Test runner (pytest, jest, unittest)
- · Linter
- · Type checker
Preconditions
Existing test coverage for target code, clear understanding of callers and dependencies
Failure modes
No tests exist before refactoring, tests break mid-refactor, external API changes, behavior changes without noticing
Trust signals
- · Small step-by-step approach
- · Test after each step
- · Never mixes refactoring with behavior changes