AI SummaryUse this skill whenever you are about to rename, restructure, extract, or otherwise refactor code in a project indexed by trace-mcp. The goal is to never break cross-file references and never guess at what is affected. This returns the risk level of the target change based on churn, complexity, fan-
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "trace-mcp-refactoring" skill in my project. Please run this command in my terminal: # Install skill into your project mkdir -p .claude/skills/trace-mcp-refactoring && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/trace-mcp-refactoring/SKILL.md "https://raw.githubusercontent.com/nikolai-vysotskyi/trace-mcp/master/skills/trace-mcp-refactoring/SKILL.md" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
Description
Safe refactoring workflow using trace-mcp — assess risk, find candidates, check impact, and rename symbols across all files without missing import sites or cross-file references.
trace-mcp — Refactoring Workflow
Use this skill whenever you are about to rename, restructure, extract, or otherwise refactor code in a project indexed by trace-mcp. The goal is to never break cross-file references and never guess at what is affected.
When to Use
• Renaming a class, function, method, variable, or file • Extracting a function or method • Restructuring a module or splitting a file • Changing a function signature • Any change that touches more than one call site
1. Assess before touching anything
` assess_change_risk({ file_path: "src/foo.ts" })
or
assess_change_risk({ symbol_id: "<id>" }) ` This returns the risk level of the target change based on churn, complexity, fan-in/fan-out, and test coverage. Use it to decide whether to proceed, add tests first, or split the change.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster