rp-refactor

rp-refactor

Use this for safe behavior-preserving improvements to code organization, duplication, or complexity.

Check workspace binding first. On mismatch, pass root=<absolute path> on every rp-mini tool call. If a shell is available and no MCP client is loaded, use node packages/server/dist/cli.js tool <workspace> <tool> --json-args '...' or its wrappers.

1. Clarify first: if the target area, behavior-preservation boundary, or acceptable risk is ambiguous, ask with AskUserQuestion before spawning the builder.
2. Do a quick scan of the named areas with get_file_tree, file_search, or get_code_structure.
3. Spawn the context-builder subagent with:
   • task: analyze the target area for refactoring opportunities while preserving behavior
   • budget: default discovery budget unless caller supplied a hard budget
   • response_type: review
   • enhancement mode: rewrite unless the user requested augment or preserve
4. If the review identifies concrete work, spawn or rerun context-builder with response_type: plan for the chosen refactor.
5. If the builder returns <questions>, follow the question loop defined in rp-build/rp-investigate before continuing.
6. Act on the handoff: implement scoped improvements only, one logical change at a time.
7. Validate behavior with existing and targeted tests; broaden tests if shared contracts changed.
8. Report what changed, what stayed intentionally unchanged, validations, and residual risk.

Do not use refactor as a vehicle for unrelated cleanup.