๐ŸŽฏ

rust-refactor-helper

๐ŸŽฏSkill

from actionbook/rust-skills

VibeIndex|
What it does

Performs safe Rust refactoring by analyzing symbol references, dependencies, and potential impacts using Language Server Protocol (LSP) operations.

๐Ÿ“ฆ

Part of

actionbook/rust-skills(35 items)

rust-refactor-helper

Installation

Quick InstallInstall with npx
npx skills add ZhangHanDong/rust-skills
CargoRun with Cargo (Rust)
cargo install cowork
git cloneClone repository
git clone https://github.com/ZhangHanDong/rust-skills.git
Add MarketplaceAdd marketplace to Claude Code
/plugin marketplace add ZhangHanDong/rust-skills
๐Ÿ“– Extracted from docs: actionbook/rust-skills
16Installs
-
AddedFeb 4, 2026

Skill Details

SKILL.md

"Safe Rust refactoring with LSP analysis. Triggers on: /refactor, rename symbol, move function, extract, ้‡ๆž„, ้‡ๅ‘ฝๅ, ๆๅ–ๅ‡ฝๆ•ฐ, ๅฎ‰ๅ…จ้‡ๆž„"

Overview

# Rust Refactor Helper

Perform safe refactoring with comprehensive impact analysis.

Usage

```

/rust-refactor-helper [--dry-run]

```

Actions:

  • rename - Rename symbol
  • extract-fn - Extract to function
  • inline - Inline function
  • move - Move to module

Examples:

  • /rust-refactor-helper rename parse_config load_config
  • /rust-refactor-helper extract-fn src/main.rs:20-35
  • /rust-refactor-helper move UserService src/services/

LSP Operations Used

Pre-Refactor Analysis

```

# Find all references before renaming

LSP(

operation: "findReferences",

filePath: "src/lib.rs",

line: 25,

character: 8

)

# Get symbol info

LSP(

operation: "hover",

filePath: "src/lib.rs",

line: 25,

character: 8

)

# Check call hierarchy for move operations

LSP(

operation: "incomingCalls",

filePath: "src/lib.rs",

line: 25,

character: 8

)

```

Refactoring Workflows

1. Rename Symbol

```

User: "Rename parse_config to load_config"

โ”‚

โ–ผ

[1] Find symbol definition

LSP(goToDefinition)

โ”‚

โ–ผ

[2] Find ALL references

LSP(findReferences)

โ”‚

โ–ผ

[3] Categorize by file

โ”‚

โ–ผ

[4] Check for conflicts

- Is 'load_config' already used?

- Are there macro-generated uses?

โ”‚

โ–ผ

[5] Show impact analysis (--dry-run)

โ”‚

โ–ผ

[6] Apply changes with Edit tool

```

Output:

```

Rename: parse_config โ†’ load_config

Impact Analysis

Definition: src/config.rs:25

References found: 8

| File | Line | Context | Change |

|------|------|---------|--------|

| src/config.rs | 25 | pub fn parse_config( | Definition |

| src/config.rs | 45 | parse_config(path)? | Call |

| src/main.rs | 12 | config::parse_config | Import |

| src/main.rs | 30 | let cfg = parse_config( | Call |

| src/lib.rs | 8 | pub use config::parse_config | Re-export |

| tests/config_test.rs | 15 | parse_config("test.toml") | Test |

| tests/config_test.rs | 25 | parse_config("") | Test |

| docs/api.md | 42 | parse_config | Documentation |

Potential Issues

โš ๏ธ Documentation reference: docs/api.md:42 may need manual update

โš ๏ธ Re-export: src/lib.rs:8 - public API change

Proceed?

  • [x] --dry-run (preview only)
  • [ ] Apply changes

```

2. Extract Function

```

User: "Extract lines 20-35 in main.rs to a function"

โ”‚

โ–ผ

[1] Read the selected code block

โ”‚

โ–ผ

[2] Analyze variables

- Which are inputs? (used but not defined in block)

- Which are outputs? (defined and used after block)

- Which are local? (defined and used only in block)

โ”‚

โ–ผ

[3] Determine function signature

โ”‚

โ–ผ

[4] Check for early returns, loops, etc.

โ”‚

โ–ผ

[5] Generate extracted function

โ”‚

โ–ผ

[6] Replace original code with call

```

Output:

```

Extract Function: src/main.rs:20-35

Selected Code

โ€‹```rust

let file = File::open(&path)?;

let mut contents = String::new();

file.read_to_string(&mut contents)?;

let config: Config = toml::from_str(&contents)?;

validate_config(&config)?;

โ€‹```

Analysis

Inputs: path: &Path

Outputs: config: Config

Side Effects: File I/O, may return error

Extracted Function

โ€‹```rust

fn load_and_validate_config(path: &Path) -> Result {

let file = File::open(path)?;

let mut contents = String::new();

file.read_to_string(&mut contents)?;

let config: Config = toml::from_str(&contents)?;

validate_config(&config)?;

Ok(config)

}

โ€‹```

Replacement

โ€‹```rust

let config = load_and_validate_config(&path)?;

โ€‹```

```

3. Move Symbol

```

User: "Move UserService to src/services/"

โ”‚

โ–ผ

[1] Find symbol and all its dependencies

โ”‚

โ–ผ

[2] Find all references (callers)

LSP(findReferences)

โ”‚

โ–ผ

[3] Analyze import changes needed

โ”‚

โ–ผ

[4] Check for circular dependencies

โ”‚

โ–ผ

[5] Generate move plan

```

Output:

```

Move: UserService โ†’ src/services/user.rs

Current Location

src/handlers/auth.rs:50-120

Dependencies (will be moved together)

  • struct UserService (50-80)
  • impl UserService (82-120)
  • const DEFAULT_TIMEOUT (48)

Import Changes Required

| File | Current | New |

|------|---------|-----|

| src/main.rs | use handlers::auth::UserService | use services::user::UserService |

| src/handlers/api.rs | use super::auth::UserService | use crate::services::user::UserService |

| tests/auth_test.rs | use crate::handlers::auth::UserService | use crate::services::user::UserService |

New File Structure

โ€‹```

src/

โ”œโ”€โ”€ services/

โ”‚ โ”œโ”€โ”€ mod.rs (NEW - add pub mod user;)

โ”‚ โ””โ”€โ”€ user.rs (NEW - UserService moved here)

โ”œโ”€โ”€ handlers/

โ”‚ โ””โ”€โ”€ auth.rs (UserService removed)

โ€‹```

Circular Dependency Check

โœ… No circular dependencies detected

```

Safety Checks

| Check | Purpose |

|-------|---------|

| Reference completeness | Ensure all uses are found |

| Name conflicts | Detect existing symbols with same name |

| Visibility changes | Warn if pub/private scope changes |

| Macro-generated code | Warn about code in macros |

| Documentation | Flag doc comments mentioning symbol |

| Test coverage | Show affected tests |

Dry Run Mode

Always use --dry-run first to preview changes:

```

/rust-refactor-helper rename old_name new_name --dry-run

```

This shows all changes without applying them.

Related Skills

| When | See |

|------|-----|

| Navigate to symbol | rust-code-navigator |

| Understand call flow | rust-call-graph |

| Project structure | rust-symbol-analyzer |

| Trait implementations | rust-trait-explorer |

More from this repository10

๐Ÿช
actionbook-rust-skills๐ŸชMarketplace

Comprehensive Rust development assistant with meta-question routing, coding guidelines, version queries, and ecosystem support

๐ŸŽฏ
coding-guidelines๐ŸŽฏSkill

Provides comprehensive Rust coding guidelines covering naming conventions, best practices, error handling, memory management, concurrency, and code style recommendations.

๐ŸŽฏ
m09-domain๐ŸŽฏSkill

Guides domain modeling in Rust by helping identify entities, value objects, aggregates, and their ownership patterns with domain-driven design principles.

๐ŸŽฏ
m05-type-driven๐ŸŽฏSkill

Enforces compile-time type safety by preventing invalid states through type-level design techniques like newtypes, type states, and phantom types.

๐ŸŽฏ
m02-resource๐ŸŽฏSkill

Guides developers in selecting the right smart pointer and resource management strategy based on ownership, thread safety, and design constraints.

๐ŸŽฏ
rust-learner๐ŸŽฏSkill

Retrieves and provides comprehensive Rust and crate information, including versions, features, documentation, and changelogs from authoritative sources.

๐ŸŽฏ
m11-ecosystem๐ŸŽฏSkill

Guides Rust developers in selecting, integrating, and managing ecosystem dependencies with best practices and strategic decision-making.

๐ŸŽฏ
rust-trait-explorer๐ŸŽฏSkill

Explores Rust trait implementations, revealing which types implement specific traits and their implementation details using LSP.

๐ŸŽฏ
rust-call-graph๐ŸŽฏSkill

Generates and visualizes Rust function call graphs using LSP, revealing function relationships and call hierarchies.

๐ŸŽฏ
m12-lifecycle๐ŸŽฏSkill

Guides resource lifecycle design by analyzing creation, usage, cleanup strategies, and ownership patterns for efficient and safe resource management in Rust.