rust-refactor-helper

Automate safe Rust refactoring with LSP-based impact analysis.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/yumazak/kodo --skill rust-refactor-helper-yumazak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rust-refactor-helper
Source: https://github.com/yumazak/kodo/tree/main/.agents/skills/rust-refactor-helper
Command: npx skills add https://github.com/yumazak/kodo --skill rust-refactor-helper-yumazak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Refactor Rust code safely with comprehensive impact analysis to minimize introduced bugs and regressions.

Core Features & Use Cases

  • Safe symbol rename, function extraction, and code movement with real-time impact assessment.
  • LSP-powered analysis for references, hover information, and call relationships before applying changes.
  • Real-world scenarios: coordinate refactors across modules while preserving compilation.

Quick Start

Run /rust-refactor-helper <action> <target> [--dry-run] to perform a safe refactor with LSP-guided impact analysis.

Frequently Asked Questions about rust-refactor-helper

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

FAQPage Schema
How do I safely refactor Rust code without introducing regressions?

Safe Rust refactoring requires comprehensive impact analysis to minimize introduced bugs and regressions. By utilizing LSP-powered analysis, you can assess references, hover information, and call relationships before applying any code changes.

How does LSP impact analysis work when moving functions across Rust modules?

LSP impact analysis works by gathering references, hover information, and call relationships across Rust modules before applying changes. This real-time assessment ensures symbol renaming, function extraction, and inline moves preserve compilation integrity.

Can I preview a Rust symbol rename before applying changes to my project?

Yes, you can preview a Rust symbol rename by running the refactor action with a dry-run flag. This performs LSP-guided impact analysis and reports potential effects without modifying the actual codebase.

What is the best way to extract functions and reorganize code in a Rust project?

The best way to extract functions and reorganize Rust code is using automated refactoring with LSP-based impact analysis. This approach provides precise impact reporting for function extraction and code movement while preserving compilation.

Does Rust refactoring with LSP analysis support multi-module code reorganization?

Yes, LSP-based Rust refactoring supports multi-module code reorganization. It coordinates refactors across modules by analyzing references and call relationships, ensuring that symbol renaming and inline moves maintain compilation integrity.