refactor-code

Plan and execute graph-powered code refactoring with blast-radius awareness.

8|3|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/demon24ru/code-review-graph --skill refactor-code-demon24ru
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: refactor-code
Source: https://github.com/demon24ru/code-review-graph/tree/main/skills/refactor-code
Command: npx skills add https://github.com/demon24ru/code-review-graph --skill refactor-code-demon24ru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Refactor planning and execution can be risky without context; this skill uses a knowledge graph to plan code changes, surface dead code, and provide a safe preview before applying.

Core Features & Use Cases

  • Graph-powered refactor planning with blast-radius awareness.
  • Workspace audit to surface dead code, large functions, and circular imports.
  • Safe rename previews, decomposition guidance, and cross-file impact analysis, with SCIP export for interoperability.

Quick Start

Start by auditing your workspace, then preview a rename or refactor before applying.

Frequently Asked Questions about refactor-code

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely refactor code across multiple files in a large codebase?▼

Safe code refactoring across large codebases requires graph-powered blast-radius awareness to preview cross-file impact. You plan changes using a knowledge graph to analyze dependencies before applying renames or structural modifications.

How do I find and remove dead code from my project workspace?▼

Dead code discovery happens through a workspace audit that analyzes the code graph to surface unused functions and imports. This process identifies unreachable code paths before you plan refactoring or deletion strategies.

Can I preview a rename refactoring before applying it to the codebase?▼

Yes, rename previews are generated by analyzing the code graph to show all affected references and cross-file impacts. You review the blast radius of the proposed rename before executing the actual code modifications.

What is a blast-radius analysis in the context of code refactoring?▼

Blast-radius analysis identifies all files and functions affected by a proposed refactoring change by traversing the code graph. It calculates the scope of impact to prevent unexpected breakages during workspace modifications.

Does this code refactoring approach work with large codebases?▼

Graph-powered refactoring is designed for large codebases where manual cross-file impact analysis is impractical. The knowledge graph scales to track complex dependencies, circular imports, and large functions across extensive workspaces.

How do I export the code graph state for interoperability?▼

You export the analyzed code graph state using SCIP export functionality. This shares the workspace health check results and dependency mappings with other compatible tools in your development workflow.