Refactoring Code
Use when semantic refactoring is needed in Rider-supported solutions and projects, including .NET/C#, F#, VB, C++, Unity, Unreal Engine, XAML, Razor, and other GameDev or mixed-language projects. Trigger when edits must update declarations and usages across IDE-resolved references — rename symbols, move types or namespaces, safe-delete unused code, extract interface/base class/method, change signatures, or reorganize namespaces. Do not use for file-only moves, config keys, strings, comments, prose-only edits, generated output, or logic changes with unchanged names/signatures.
Install
npx skills add JetBrains/skills --skill refactoring-codegit clone --depth 1 https://github.com/JetBrains/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/refactoring-code ~/.claude/skills/refactoring-codePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Code Refactoring Rider/ReSharper-driven semantic refactorings across solutions opened in Rider. Each tool resolves the target through the IDE's reference index and rewrites every affected site — language-aware usages such as `nameof`, XML-doc `<see cref>`, XAML `x:Name`, Razor, C++/Unreal references, and ordinary references that grep cannot resolve — instead of a grep + text replace. ## Invoking a tool Always call a refactoring tool **through `execute_tool`** — direct calls are not routed: ``` execute_tool(command="<tool> --arg value [--flag true]") ``` [reference/tools.md](reference/tools.md) lists every available tool; the linked `reference/tools/<tool>.md` gives the exact parameters, response shape, outcomes, and error kinds for the one tool you are about to call. Read only that one — do not pre-load the whole tree. ## Shared rules 1. **Prefer the MCP tool.** It resolves references semantically across the solution; a text edit cannot. On any error you cannot fix by adjusting the input, or when `execute_tool` is unavailable, fall back to a text-based edit. 2. **Trust the success signal.** When a tool reports success, do not re-read the mutated files to verify. When a tool reports a count of touched/affected sites, a value of **1** for a type, method, property, field, or namespace is suspicious (declaration only, no callers) — surface it to the user.
Details
- Skill name
refactoring-code- Repository
- JetBrains/skills
- Path
refactoring-code/SKILL.md- Repo updated
- 21 October 2026
FAQ
What does the Refactoring Code skill do?
Use when semantic refactoring is needed in Rider-supported solutions and projects, including .NET/C#, F#, VB, C++, Unity, Unreal Engine, XAML, Razor, and other GameDev or mixed-language projects. Trigger when edits must update declarations and usages across IDE-resolved references — rename symbols, move types or namespaces, safe-delete unused code, extract interface/base class/method, change signatures, or reorganize namespaces. Do not use for file-only moves, config keys, strings, comments, prose-only edits, generated output, or logic changes with unchanged names/signatures.
How do I install the Refactoring Code skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add JetBrains/skills --skill refactoring-code. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Refactoring Code popular?
It lives in JetBrains/skills, which has 398 GitHub stars and 35 forks.
Related skills
Deploy to Vercel
398JetBrains/skills
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".
Vercel React Native Skills
398JetBrains/skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
Vitest
398JetBrains/skills
Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.
Sentry
398JetBrains/skills
Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.
Prophetx
271machina-sports/sports-skills
ProphetX betting exchange — public tournaments, events, markets, and exchange odds. No API key, read-only. Covers soccer, tennis, basketball, MLB, NFL, NHL. IMPORTANT: odds are optional per market — shown only when a public order book exists (check `selections_available`); empty/suspended books return market structure and matched stake only. Guaranteed odds coverage requires the authenticated ProphetX Affiliate API (separate Machina connector). Use when: user asks what markets/lines ProphetX offers for a game, exchange odds and order-book prices (when exposed), event/tournament discovery, mark
Skillshare Codebase Audit
398JetBrains/skills
Cross-validate CLI flags, docs, tests, and targets for consistency across the codebase. Use this skill whenever the user asks to: audit the codebase, check for consistency issues, find undocumented flags, verify test coverage, validate targets.yaml, check handler split conventions, or verify oplog instrumentation. This is a read-only audit — it reports issues but never modifies files. Use after large refactors, before releases, or whenever you suspect docs/code/tests have drifted out of sync.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.