rust-refactor-helper

Name: rust-refactor-helper
Availability: InStock
Author: simorgh3196

Refactor Rust code with LSP-driven impact analysis and dry-run reports.

1|Updated May 29, 2026

Search Tags:#refactoring #rust #rename #lsp #code-analysis #extract-function

Ready to run

npx skills add https://github.com/simorgh3196/tsuzulint --skill rust-refactor-helper

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rust-refactor-helper
Source: https://github.com/simorgh3196/tsuzulint/tree/main/.agents/skills/rust-refactor-helper
Command: npx skills add https://github.com/simorgh3196/tsuzulint --skill rust-refactor-helper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Refactor Rust code safely with LSP-driven impact analysis.

Core Features & Use Cases

Pre-refactor analysis: Analyze symbol references and potential impact before changes.
Multi-file refactoring: Rename, extract function, inline, and move across modules with conflict checks.
Safe application workflow: Generate a concrete change plan and support dry-run previews.

Quick Start

Use the rust-refactor-helper to perform a dry-run rename: /rust-refactor-helper rename parse_config load_config --dry-run

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 rename a function across a Rust project without missing references?▼

To safely rename a function across a Rust project, use LSP-driven reference discovery to find all symbol usages and perform conflict checks before applying changes. This approach analyzes potential impact across modules to ensure no references are missed.

What is the best way to preview a Rust refactoring plan before modifying the codebase?▼

The best way to preview a Rust refactoring plan is to use a dry-run report. A dry-run generates a concrete change plan and analyzes symbol references without applying modifications, allowing you to verify the impact safely.

Can I extract a function and move code between modules in Rust using LSP?▼

Yes, you can extract a function and move code between modules in Rust using LSP. The refactoring process targets extract function, inline, and move operations across multi-file codebases with comprehensive reference discovery and conflict checks.

Do I need an LSP-capable environment to perform Rust code analysis for refactoring?▼

Yes, you need an LSP-capable environment and an existing Rust project to perform code analysis for refactoring. The refactoring workflow requires LSP insight to execute pre-refactor analysis, change generation, and reference discovery.

Why does my Rust multi-file rename operation fail due to conflicts?▼

A Rust multi-file rename operation fails due to conflicts when pre-refactor analysis detects clashing symbol references. Performing LSP-driven impact analysis before changes helps identify these conflicts across modules and prevents unsafe application.