Home / Companies / JetBrains / Blog / Post Details
Content Deep Dive

Rider Hands AI Agents The Keys To Its Refactoring Engine For Safer, Faster, And Cheaper Results - The JetBrains Blog

Blog post from JetBrains

Post Details
Company
Date Published
Author
Sasha Ivanova
Word Count
1,521
Company Posts That Month
42
Language
American English
Hacker News Points
-
Post removed?
No
Summary

JetBrains Rider 2026.2.1 introduces a bundled refactoring-code skill that lets AI agents invoke Rider’s ReSharper-powered C# refactoring engine rather than attempting structural changes through text edits and repeated compiler checks. In an evaluation of 15 tasks covering eight refactoring types, including renaming symbols, extracting methods or interfaces, changing API signatures, moving types, reorganizing namespaces, and safe deletion, access to the skill reduced median task time from 157.9 to 26.6 seconds, cost per solved task from $0.52 to $0.19, and tool calls per task from 17.0 to 6.2. The comparison used the same model, prompts, and approximately ten runs per task, differing only in whether the Rider skill was available. Without it, the model frequently relied on text-processing commands, Git, and 163 build calls to discover errors caused by edits; with it, build calls dropped to three because Rider can resolve symbols, references, overloads, and dependencies directly through its syntax model. The skill improved eight tasks substantially, particularly complex extraction and relocation operations, though some already-fast tasks saw limited benefit and several were not solved by one or both approaches. Rider activates the capability automatically for C# refactoring requests, with specific instructions such as extracting an interface or renaming a symbol expected to make use of the available IDE operation.

Trends Found in this Post

No tracked trend matches for this post yet.

Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.