Rust Refactor Helper
Rename, extract, inline, or move Rust symbols with LSP-backed reference analysis and optional dry-run before applying edits.
Overview
Rust Refactor Helper is an agent skill for the Build phase that performs LSP-analyzed Rust refactors including rename, extract, inline, and move with dry-run support.
Install
npx skills add https://github.com/zhanghandong/rust-skills --skill rust-refactor-helperWhat is this skill?
- Actions: rename, extract-fn, inline, and move symbols across modules
- Uses LSP findReferences, goToDefinition, hover, and incomingCalls before mutating code
- Supports --dry-run for impact preview
- Argument hint: action, target, optional dry-run flag
- Triggers on /refactor, rename symbol, 重构, 重命名, 提取函数
- 4 refactor actions: rename, extract-fn, inline, move
Adoption & trust: 773 installs on skills.sh; 1.2k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need to rename or reorganize Rust code but fear breaking callers the compiler will only surface after a long feedback loop.
Who is it for?
Solo Rust developers using agentic IDEs with LSP who regularly rename APIs or extract functions in growing codebases.
Skip if: Greenfield prototypes with no rust-analyzer/LSP setup or one-line cosmetic edits where manual change is faster.
When should I use this skill?
/refactor, rename symbol, move function, extract, 重构, 重命名, 提取函数, 安全重构
What do I get? / Deliverables
You get reference-aware refactors across the crate tree, with dry-run previews when you want confidence before Edit applies changes.
- Applied multi-file edits or dry-run impact summary
- Reference-categorized change plan per file
Recommended Skills
Journey fit
Build is where structural code changes happen; this skill is a refactoring workstation during active development, not a ship-time audit. Backend fits Rust services, libraries, and systems code where module moves and symbol renames have wide compile-time blast radius.
How it compares
LSP-guided refactor workflow—not a cargo clippy lint pack or automated migration framework.
Common Questions / FAQ
Who is rust-refactor-helper for?
Indie and solo Rust builders who use AI agents with LSP access and need disciplined rename, extract, inline, and move operations.
When should I use rust-refactor-helper?
During Build on backend or library code when restructuring modules, renaming public symbols, or extracting functions from large handlers.
Is rust-refactor-helper safe to install?
It can Edit project files—use --dry-run first and review the Security Audits panel on this Prism page before granting write access in CI or shared repos.
SKILL.md
READMESKILL.md - Rust Refactor Helper
# Rust Refactor Helper Perform safe refactoring with comprehensive impact analysis. ## Usage ``` /rust-refactor-helper <action> <target> [--dry-run] ``` **Actions:** - `rename <old> <new>` - Rename symbol - `extract-fn <selection>` - Extract to function - `inline <fn>` - Inline function - `move <symbol> <dest>` - 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<Config> { 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 │