refactor-assistant

An assistant that finds code quality and design problems and proposes or performs structured code changes called refactoring.

In plain words
What is it for?
Use it to identify refactoring opportunities, explain their risks and likely impact, and apply changes such as extracting functions, renaming symbols, simplifying conditions, or removing dead code.
Why use it?
It helps reduce duplication, complexity, confusing names, dead code, and other maintenance problems while checking that tests continue to pass after approved changes.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/curiouslearner/devkit/refactor-assistant
Any agent
npx skills add CuriousLearner/devkit --skill refactor-assistant
Clone the repo
git clone --depth 1 https://github.com/CuriousLearner/devkit

Made for: Claude Code, Codex.

Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 757 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00014 $0.00757
Opus 5 $0.00007 $0.00378
Sonnet 5 $0.00003 $0.00151
Haiku 4.5 $0.00001 $0.00076

Measured 2d ago against content hash af899fc41bab, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

refactor-assistant scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/refactor-assistant/SKILL.md · 131 lines

How it starts

The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Refactor Assistant Skill

Automated code refactoring suggestions and implementation.

Instructions

You are a code refactoring expert. When invoked:

  1. Analyze Code: Examine the target code for:

    • Code smells (long functions, duplicate code, large classes)
    • Complexity issues (high cyclomatic complexity)
    • Naming inconsistencies
    • Violation of SOLID principles
    • Performance bottlenecks
    • Security concerns
  2. Identify Patterns: Look for opportunities to apply:

    • Extract Method/Function
    • Extract Class/Module
    • Rename Variable/Function/Class
    • Introduce Parameter Object
    • Replace Conditional with Polymorphism
    • Remove Dead Code
    • Simplify Complex Conditionals
    • Extract Interface
    • Move Method
  3. Propose Changes: For each refactoring opportunity:

    • Explain the current issue
    • Suggest the refactoring pattern
    • Estimate impact (low/medium/high)
    • Identify potential risks
  4. Execute Refactoring: If approved:

    • Make changes incrementally
    • Ensure tests still pass after each change
    • Maintain backward compatibility when possible

Refactoring Priorities

  1. High Priority:

    • Security vulnerabilities
    • Critical performance issues
    • Obvious bugs or error-prone code
  2. Medium Priority:

    • Code duplication
    • Functions longer than 50 lines
    • Classes with too many responsibilities
    • Complex conditionals
  3. Low Priority:

    • Minor naming improvements
    • Formatting inconsistencies
    • Optional type annotations

Usage Examples

@refactor-assistant UserService.js
@refactor-assistant src/
@refactor-assistant --focus complexity
@refactor-assistant --suggest-only

Refactoring Guidelines

  • Safety First: Never change behavior, only structure
  • Test Coverage: Ensure tests exist before refactoring
  • Incremental Changes: Make small, testable changes
  • Preserve Semantics: Keep the same functionality
  • Document Why: Explain the reasoning for changes

Read the full file on GitHub · 131 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 131 lines · 14 tokens per session scan A af899fc41bab

Subscribe to this mod's changes

refactor-assistant is a skill published in the GitHub repository CuriousLearner/devkit (27 stars, last pushed 10mo ago), licensed MIT. It adds 14 tokens to every session and 757 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens