I’m looking at using Claude Code for a refactor that touches several modules in an older repository. The codebase has some tests, but not enough to catch every behavioral edge case, so a patch that looks clean could still break a less obvious path.
How do you keep this kind of work reviewable? I’d be interested in experiences with splitting the task into smaller changes, asking Claude to map dependencies first, or using other checks before trusting the refactor.
Can you answer this question?
Write Answer0 Answers