Refactor code across files using LSP-based reference analysis.
npx skills add https://github.com/foundry-works/claude-foundry --skill foundry-refactor
Please help me install this Agent Skill. Skill: foundry-refactor Source: https://github.com/foundry-works/claude-foundry/tree/main/skills/foundry-refactor Command: npx skills add https://github.com/foundry-works/claude-foundry --skill foundry-refactor
Cross-file symbol refactoring is error-prone and time-consuming. This skill provides a safe, LSP-powered workflow that analyzes references before making changes, ensuring updates propagate correctly and reducing drift.
To use this skill, initiate a refactor task (rename, extract, or move) in a project with LSP support and the Claude Code environment, then follow the prompts to scope, validate references, execute changes, and verify results.
High-intent search queries and answers about installing and using this skill.
Safe cross-file rename requires LSP-based analysis to find all references before propagating symbol changes. This approach validates references first, ensuring updates propagate correctly across files and reducing drift.
Extracting a function safely uses LSP guidance to identify references and update them during the extraction. This ensures the newly extracted method or function is wired correctly across the codebase without manual searching.
Moving a symbol across files requires updating all import statements and references in the target and source files. LSP analysis finds affected locations to execute the move and update imports comprehensively.
Yes, LSP tooling is required. Cross-file refactoring relies on documentSymbol, findReferences, and goToDefinition capabilities to analyze the codebase and ensure safe, comprehensive reference updates before applying changes.
Optional dead code cleanup is supported during refactoring. After moving or renaming symbols, reference analysis identifies unused code, allowing you to safely remove it within the spec-driven workflow.
A spec-driven refactoring workflow structures changes through planning, verification, and journaling phases. It uses mcp-based task journaling to track each step, ensuring LSP-guided symbol changes are validated and recorded.
wgordon17Navigate codebases with LSP for semantic symbol resolution and go-to-definition.
mikkerRemove dead code and simplify logic while preserving build and test behavior.
danalexilewisGenerate structured plan files with YAML frontmatter under plans/.
sachmataModify source code via symbol-aware and regex-based operations through the Serena MCP server.
