Imported from tirth8205/code-review-graph (
skills/refactor-safely/SKILL.md) via skills.sh. Install upstream withnpx skills add tirth8205/code-review-graph --skill refactor-safely. Copyright stays with the author.
Refactor Safely
Plan a refactor from the dependency graph and apply renames from a preview.
Steps
- Call
refactor_toolwithmode="suggest"for refactoring candidates, ormode="dead_code"for unreferenced code. - For a rename, call
refactor_toolwithmode="rename",old_nameandnew_name. Check the returned edit list before applying. - Call
apply_refactor_toolwith the returnedrefactor_idto apply the rename. - Before a large refactor, call
get_impact_radius_toolandget_affected_flows_toolto see the dependents and critical paths involved. - Call
find_large_functions_toolto find functions worth splitting. - After the change, call
detect_changes_toolto confirm the impact matches the plan.
Token Efficiency Rules
- Call
get_minimal_context_tool(task="<your task>")before any other graph tool. - Pass
detail_level="minimal"unless it is not enough. Minimal drops source, so leavesemantic_search_nodes_tool(include_source=True)andget_review_context_toolat standard. - Prefer a targeted
query_graph_toolcall over a broad listing call. - Budget: about five tool calls per task. Source snippets stand in for file reads.
- Read the implementation and its tests before changing code. The graph narrows scope; it does not replace the source.
