Slash Command

/refactor

Safely refactor code with verification at each step.

Install

npx claudepluginhub radenadri/skills-alena

Flags

No model invocation

Details

Argument[file-or-pattern-to-refactor]

Prompt Preview

# /refactor — Safe Refactoring

Refactor code while maintaining correctness through continuous verification.

## Instructions

1. **Assess the target** from `$ARGUMENTS`:
   - Read and understand the current code
   - Identify code smells: duplication, long functions, god classes, deep nesting
   - Map all callers and dependents of the code being refactored

2. **Establish a safety net**:
   - Run existing tests: `npm test` / `pytest` / etc.
   - If no tests exist → WRITE CHARACTERIZATION TESTS FIRST
   - Note the current test results as the baseline

3. **Plan the refactoring** — choose fr...

Command Content

Other plugins with /refactor

/refactor

Orchestrates refactoring for specified scope: assesses architecture and issues, plans incremental transformations with risk mitigation, provides code change guides with examples, validation tests, and monitoring plan.

essentials

2.4k

/refactor

architecture/

Systematically refactors target code area: identifies smells like long functions and duplicates, verifies/adds tests, plans atomic steps, executes with verification, preserves behavior.

claude-code-toolkit

1.4k

/refactor

Safely refactors code progressively using techniques like Extract Method, quantitatively scores SOLID principle adherence (0-100), visualizes technical debt, and prioritizes improvements.

cook-fr

889

/refactor

Safely refactors code gradually, quantitatively scores SOLID principles adherence (0-100 per principle), detects smells and debt, and prioritizes improvements with techniques like Extract Method.

cook-pt

889

/refactor

Safely refactors code gradually using techniques like Extract Method, scores SOLID adherence (0-100), visualizes technical debt, and prioritizes improvements.

cook-es

889

/refactor

Performs safe incremental refactoring on code, scores SOLID principles compliance (0-100 total), detects smells via grep/bash, visualizes technical debt, and prioritizes fixes with examples.

cook-zh-cn

889

Stats

Stars0

Forks0

Last CommitMar 30, 2026

Used By2 plugins

Actions

View Source View Plugin View on GitHub View README

# /refactor — Safe Refactoring Refactor code while maintaining correctness through continuous verification. ## Instructions 1. **Assess the target** from `$ARGUMENTS`: - Read and understand the current code - Identify code smells: duplication, long functions, god classes, deep nesting - Map all callers and dependents of the code being refactored 2. **Establish a safety net**: - Run existing tests: `npm test` / `pytest` / etc. - If no tests exist → WRITE CHARACTERIZATION TESTS FIRST - Note the current test results as the baseline 3. **Plan the refactoring** — choose fr...

/refactor — Safe Refactoring

Refactor code while maintaining correctness through continuous verification.

Instructions

Assess the target from $ARGUMENTS:

Read and understand the current code
Identify code smells: duplication, long functions, god classes, deep nesting
Map all callers and dependents of the code being refactored

Establish a safety net:

Run existing tests: npm test / pytest / etc.
If no tests exist → WRITE CHARACTERIZATION TESTS FIRST
Note the current test results as the baseline

Plan the refactoring — choose from:

Extract function — pull logic into a named function
Extract class — separate responsibilities
Rename — improve naming for clarity
Move — relocate code to better module
Inline — remove unnecessary abstraction
Replace conditional with polymorphism
Introduce parameter object — group related params

Execute in small steps:

Make ONE refactoring move at a time
Run tests after EACH move
If tests fail → revert and try a different approach
Commit after each successful step

Verify the refactoring:

All existing tests still pass
No new warnings or errors
Code is measurably simpler (fewer lines, less nesting, better names)
All callers still work correctly

NEVER combine refactoring with behavior changes — do one or the other.

/refactor — Safe Refactoring

Refactor code while maintaining correctness through continuous verification.

Instructions

Assess the target from $ARGUMENTS:
- Read and understand the current code
- Identify code smells: duplication, long functions, god classes, deep nesting
- Map all callers and dependents of the code being refactored
Establish a safety net:
- Run existing tests: npm test / pytest / etc.
- If no tests exist → WRITE CHARACTERIZATION TESTS FIRST
- Note the current test results as the baseline
Plan the refactoring — choose from:
- Extract function — pull logic into a named function
- Extract class — separate responsibilities
- Rename — improve naming for clarity
- Move — relocate code to better module
- Inline — remove unnecessary abstraction
- Replace conditional with polymorphism
- Introduce parameter object — group related params
Execute in small steps:
- Make ONE refactoring move at a time
- Run tests after EACH move
- If tests fail → revert and try a different approach
- Commit after each successful step
Verify the refactoring:
- All existing tests still pass
- No new warnings or errors
- Code is measurably simpler (fewer lines, less nesting, better names)
- All callers still work correctly
NEVER combine refactoring with behavior changes — do one or the other.