Refactoring Agent Skill

Identify and apply targeted refactoring improvements to existing code without changing behavior.

Context cost
275 tokensestimated from the bundle, loaded when it triggers
Bundle
1 file · 1.1 kBtext throughout, nothing executable
Licence
not declarednone named by its author
Last change
—no release on file
Servers it uses
Noneruns standalone

What it does

Identify and apply targeted refactoring improvements to existing code without changing behavior

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

developer toolsengineeringqualityrefactoring

The skill itself

A skill is instructions the model reads, and here they are in full: the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md1.1 kB
--- name: Refactoring tags: [engineering, quality, refactoring] audience: [engineers, tech-leads] status: draft ---
9# Refactoring
10
11You are an expert software engineer specializing in code refactoring. Your goal is to improve code structure, readability, and maintainability **without changing observable behavior**.
12
13## Process
14
151. **Understand intent** — read the code and summarize what it does before suggesting changes
162. **Identify smells** — duplication, long methods, feature envy, data clumps, primitive obsession
173. **Propose refactors** — name the pattern (Extract Method, Replace Conditional with Polymorphism, etc.)
184. **Show the change** — provide a before/after diff or the refactored version
19
20## Rules
21
22- Never change behavior — if a refactor requires changing tests, flag it explicitly
23- Apply one refactoring at a time; do not chain multiple changes without explanation
24- If the code has no tests, warn before suggesting structural changes
25- Prefer small, incremental changes over large rewrites
26
This is the whole of SKILL.md. Install the skill to get it and everything beside it.
In the file
SKILL.md159 words
Files1
Licencenot declared
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈60
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
215
on trigger
The instruction body, read only when the skill fires.
0.14%
of a 200k window
Ten skills this size would take about 1% of the window before you open a file.
050k100k150k200k context window

275 tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Small enough to keep loaded permanently without thinking about it.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md, shown in full above.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

Its SKILL.md does not declare which tools it asks the agent for, so what it touches is whatever the instructions themselves ask for — read them before you install it.

What it asks for
Writes filesnot declared
Network accessnot declared

This SKILL.md carries no allowed-tools line, so neither is declared. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

1 file, 1.1 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md1.1 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 1 file you can review in full before installing.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Refactoring · 275 tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/refactoring/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/refactoring" ] && { [ ! -e .claude/skills/refactoring ] || { mv .claude/skills/refactoring "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/refactoring" .claude/skills/ && echo "Installed .claude/skills/refactoring"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add singleton-sd/refactoring

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/refactoring/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/refactoring/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/refactoring" ] && { [ ! -e ~/.claude/skills/refactoring ] || { mv ~/.claude/skills/refactoring "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/refactoring" ~/.claude/skills/ && echo "Installed ~/.claude/skills/refactoring" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/refactoring/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where. It appears as Refactoring in Gemini CLI, Codex, Copilot and Grok (its own name); Claude Code lists it by the folder name, refactoring.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Versionnot versioned
Publishedno release date on file
PriceFree
Referencesingleton-sd/refactoring

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Publisher
Servers0
Claim this skill