mcpbeat Sign in

Code Refactor Skill for Claude

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.

839 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
656
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/mhattingpete/claude-skills-marketplace --skill code-refactor

The instruction itself

14 sections, as written by the author

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

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

Replace Deprecated Pattern

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

Update API Calls

  • Find: Grep(pattern="/api/auth/login", output_mode="content", -n=true)
  • Replace: Edit(old_string="'/api/auth/login'", new_string="'/api/v2/authentication/login'", replace_all=true)
  • 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:

  • Search → Find all
  • Analyze → Verify appropriate
  • Inform → Tell user scope
  • Execute → Make changes
  • Verify → Confirm applied
  • 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

Other skills for the same job

different authors, same section of the catalogue
Git Commit
by github
vendor ×3

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

799 tokens
Github Code Review
by ComeOnOliver
×3

Comprehensive GitHub code review with AI-powered swarm coordination

13k tokens
Commit Work
by softaworks
×2

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

2k tokens
Verification & Quality Assurance
by Microck
×2

Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.

4k tokens
Gh CLI
by christophacham
×2

GitHub CLI (gh) comprehensive reference for repositories, issues, pull requests, Actions, projects, releases, gists, codespaces, organizations, extensions, and all GitHub operations from the command line.

10k tokens
Github
by Dicklesworthstone
×2

GitHub CLI - manage repositories, issues, pull requests, actions, releases, and more from the command line.

1k tokens
Codebase Cleanup Refactor Clean
by ComeOnOliver
×2

You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.

9k tokens
Codebase Cleanup Tech Debt
by ComeOnOliver
×2

You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti

6k tokens

How to use it

Copy the folder

Take mhattingpete/code-refactor from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.