Skip to content
alyn
mhattingpete

Code Refactor skill

Perform bulk code refactoring operations like renaming variables/functions across files, replacing patterns, and updating API calls. Use when users request renaming identifiers, replacing deprecated code patterns, updating method calls, or making consistent changes across multiple locations.

$npx skills add mhattingpete/claude-skills-marketplace --skill code-refactor
View this skill on GitHubmhattingpete/claude-skills-marketplace/code-operations-plugin/skills/code-refactor/SKILL.md
Pack stars
694
Pack installs
6.3k
Alyn Score
47/99
Updated
4 months ago
License
Apache-2.0
– views – installs via Alyn

Install Code Refactor

Pick your agent. Every command is ready to paste.

$npx skills add mhattingpete/claude-skills-marketplace --skill code-refactor

The open skills CLI detects your agents (Claude Code, Cursor, Codex and 70+ more) and installs to the right folder. Add -g to install globally.

01

Install it

Run the command above, or upload the folder in Claude.

02

Ask naturally

Describe the task. Your agent loads code-refactor when the request matches its description.

03

Name it if needed

If it does not trigger, say “use the code-refactor skill”. In Codex, type $code-refactor.

The skill itself

SKILL.md

FolderGitHub

Code Refactor

Systematic code refactoring across files. Auto-switches to execution mode for 10+ files (90% token savings).

Mode Selection

  • 1-9 files: Use native tools (Grep + Edit with replace_all)
  • 10+ files: Automatically use code-execution skill

Execution example (50 files):

from api.code_transform import rename_identifier
result = rename_identifier('.', 'oldName', 'newName', '**/*.py')
# Returns: {'files_modified': 50, 'total_replacements': 247}
# ~500 tokens vs ~25,000 tokens traditional

When to Use

  • "rename [identifier] to [new_name]"
  • "replace all [pattern] with [replacement]"
  • "refactor to use [new_pattern]"
  • "update all calls to [function/API]"
  • "convert [old_pattern] to [new_pattern]"

Core Workflow (Native Mode)

1. Find All Occurrences

Grep(pattern="getUserData", output_mode="files_with_matches")     # Find files
Grep(pattern="getUserData", output_mode="content", -n=true, -B=2, -A=2)  # Verify with context

2. Replace All Instances

Edit(
  file_path="src/api.js",
  old_string="getUserData",
  new_string="fetchUserData",
  replace_all=true
)

3. Verify Changes

Grep(pattern="getUserData", output_mode="files_with_matches")  # Should return none

Workflow Examples

Rename Function

  1. Find: Grep(pattern="getUserData", output_mode="files_with_matches")
  2. Count: "Found 15 occurrences in 5 files"
  3. Replace in each file with replace_all=true
  4. Verify: Re-run Grep
  5. Suggest: Run tests

Replace Deprecated Pattern

  1. Find: Grep(pattern="\\bvar\\s+\\w+", output_mode="content", -n=true)
  2. Analyze: Check if reassigned (let) or constant (const)
  3. Replace: Edit(old_string="var count = 0", new_string="let count = 0")
  4. Verify: npm run lint

Update API Calls

  1. Find: Grep(pattern="/api/auth/login", output_mode="content", -n=true)
  2. Replace: Edit(old_string="'/api/auth/login'", new_string="'/api/v2/authentication/login'", replace_all=true)
  3. Test: Recommend integration tests

Best Practices

Planning:

  • Find all instances first
  • Review context of each match
  • Inform user of scope
  • Consider edge cases (strings, comments)

Safe Process:

  1. Search → Find all
  2. Analyze → Verify appropriate
  3. Inform → Tell user scope
  4. Execute → Make changes
  5. Verify → Confirm applied
  6. Test → Suggest running tests

Edge Cases:

  • Strings/comments: Ask if should update
  • Exported APIs: Warn of breaking changes
  • Case sensitivity: Be explicit

Tool Reference

Edit with replace_all:

  • replace_all=true: Replace all occurrences
  • replace_all=false: Replace only first (or fail if multiple)
  • Must match EXACTLY (whitespace, quotes)

Grep patterns:

  • -n=true: Show line numbers
  • -B=N, -A=N: Context lines
  • -i=true: Case-insensitive
  • type="py": Filter by file type

Integration

  • test-fixing: Fix broken tests after refactoring
  • code-transfer: Move refactored code
  • feature-planning: Plan large refactorings

Tips for Code Refactor

  • • Start a fresh session after installing so your agent picks up the new skill.
  • • It is part of a pack with 18 skills. Install only the ones you need with --skill to keep triggers precise.
  • • If two skills overlap, mention the one you want by name.

Questions about Code Refactor

What does the Code Refactor skill do?

Perform bulk code refactoring operations like renaming variables/functions across files, replacing patterns, and updating API calls. Use when users request renaming identifiers, replacing deprecated code patterns, updating method calls, or making consistent changes across multiple locations.

How do I install Code Refactor?

Run "npx skills add mhattingpete/claude-skills-marketplace --skill code-refactor" in your project. The skills CLI installs it for Claude Code, Cursor, Codex and 70+ other agents. In Claude on the web, upload the skill folder as a ZIP under Customize > Skills.

Does Code Refactor work in Cursor and Codex?

Yes. Code Refactor uses the open SKILL.md format, so it works in Claude Code, Claude, Cursor, OpenAI Codex, Gemini CLI, GitHub Copilot and other agents that support agent skills.

Is Code Refactor free?

Code Refactor is open source on GitHub under the Apache-2.0 license. It is free to install; check the license before commercial use.

Who made Code Refactor?

Code Refactor is published by mhattingpete in the mhattingpete/claude-skills-marketplace repository, together with 17 other skills.

Similar skills. From other creators.