---
name: Refactor Safely
slug: refactor-safely
category: Quality
description: Refactor Safely plans and executes code refactoring using dependency analysis from a knowledge graph. It helps developers safely rename symbols, remove dead code, and verify refactoring impact before and after applying changes.
github: "https://github.com/tirth8205/code-review-graph/tree/main/skills/refactor-safely"
language: Python
stars: 30048
forks: 2760
install: "npx degit https://github.com/tirth8205/code-review-graph/tree/main/skills/refactor-safely ~/.claude/skills/refactor-safely"
installs_to: ~/.claude/skills/refactor-safely
source_path: skills/refactor-safely/SKILL.md
collection_size: 7
category_size: 1354
collection_url: "https://dirskills.com/collections/tirth8205/code-review-graph"
added: 2026-08-14T07:11:48.124Z
last_synced: 2026-08-14T07:11:48.124Z
canonical_url: "https://dirskills.com/skills/refactor-safely"
---

# Refactor Safely

Refactor Safely plans and executes code refactoring using dependency analysis from a knowledge graph. It helps developers safely rename symbols, remove dead code, and verify refactoring impact before and after applying changes.

**Install:**

```bash
npx degit https://github.com/tirth8205/code-review-graph/tree/main/skills/refactor-safely ~/.claude/skills/refactor-safely
```

## README

## Refactor Safely

Use the knowledge graph to plan and execute refactoring with confidence.

### Steps

1. Use `refactor_tool` with mode="suggest" for community-driven refactoring suggestions.
2. Use `refactor_tool` with mode="dead_code" to find unreferenced code.
3. For renames, use `refactor_tool` with mode="rename" to preview all affected locations.
4. Use `apply_refactor_tool` with the refactor_id to apply renames.
5. After changes, run `detect_changes_tool` to verify the refactoring impact.

### Safety Checks

- Always preview before applying (rename mode gives you an edit list).
- Check `get_impact_radius_tool` before major refactors.
- Use `get_affected_flows_tool` to ensure no critical paths are broken.
- Run `find_large_functions` to identify decomposition targets.

## Token Efficiency Rules
- ALWAYS start with `get_minimal_context(task="<your task>")` before any other graph tool.
- Use `detail_level="minimal"` on all calls. Only escalate to "standard" when minimal is insufficient.
- Target: complete any review/debug/refactor task in ≤5 tool calls and ≤800 total output tokens.