Key features
Details built so the generated code looks like its neighbours wrote it
🎯
Refactor This menu
One keystroke lists everything applicable here, built-in refactorings alongside Refactory's; unavailable actions are listed too, with the reason.
🏠
Convention-aware
Extract Interface learns its target folder from sibling classes; underscores, this., XML docs are measured from the class being edited, not read from settings.
🔗
Solution-shaped multi-file ops
Adding an injected dependency lands six edits at once: using, field, XML doc, constructor parameter, <param> tag, assignment — one undo stop.
⚛️
React semantics
Extract component infers prop types, carries 'use client' to the new file verbatim, and exports module constants instead of duplicating them.
✏️
IDE-grade linked edit
While naming, the call site, interface, function and type reference all enter edit mode together — type once, all update.
🛡️
Refusals over features
Underivable types refuse and name the prop, dependency arrays are never modified, a manual new blocks injection — uncertainty is stated, never approximated.
⚡
Never slows the editor
No solution load, no TypeScript program; cross-file questions are answered by a declaration index and an import graph, built in under a second.
📝
Project convention file
.refactory.json is committed — conventions belong to the repository, not personal settings; anything absent is detected.
🔍
37 code-smell rules
The "compiles, but will hurt you" layer for React and C#: sync-over-async, components defined inside components, state mutated in place — traps are warnings, taste is a hint.
📊
Code Health dashboard
Scan the whole workspace (nothing opened, no Problems flood), group by file or rule, eight themes, and Copy report drops Markdown straight into a PR.
📐
Complexity and an A–F health score
Cyclomatic complexity per function, method and constructor, counted identically in both engines so a mixed repo's numbers are comparable; every file gets a 0–100 score graded A–F, plus a workspace-wide Most complex functions list.
🕰️
Scan history and trends
Every completed workspace scan stores a snapshot (last 100 kept), drawn as a trend chart with the per-rule delta since the previous run. Cancelled scans record nothing — a half-finished sweep would draw a phantom improvement.
🔥
Hotspots: churn × complexity
One git log for the whole repository, joined against the health score — frequently edited and complex ranks first. Not a git repository? The section is simply absent, never an error.
✦
Deep review briefing
✦ Review on any file or hotspot writes a Markdown briefing — metrics, churn, hotspot rank, every finding with its rule id and line — then opens your own claude session pointed at it. Review top 3 briefs the three riskiest files in one session, because "which of these first?" cannot be answered by a session that sees only one.
🤖
Fix with Claude Code
A quick fix that opens your local claude session on that smell — your login, your model, your approval flow; the extension only writes the prompt.
🧹
Clean Up This File
Applies every mechanical fix with exactly one correct answer at once (throw ex; → throw; and friends) — one undo reverts the lot.
