refactor
luongnv89/claude-howto / 03-skills/refactor
guides you through six phases before each refactor , which improves: avoids regressions and broken code
Details
- judge’s score
- 7/10
- place
- outside the packs
- publisher
- luongnv89
- status
- new
- pinned commit
- 188f468 on GitHub (new tab)
- skill’s last commit
- Aug 4, 2026
- repo stars
- 42,021
- main type
- Other
Judgement
Clear triggering and well-defined scope. The Fowler method is very well known to Claude, so little skill-specific know-how; generic commands. Annexes truncated, scripts not provided.
reservations
- Largely generic content: Fowler's methodology and the catalog of code smells are already known to Claude, with few project-specific conventions.
- Annexes references/code-smells.md and refactoring-catalog.md truncated at 5000 characters; templates and scripts not provided, so not verifiable.
- Minor contradiction: "Never refactor without tests" versus the "proceed without tests" option in phase 2.
- Considerable length for limited gain: many phases and checklists that the model would follow anyway.
- Triggering
- 2/2
- Added value
- 1/2
- Precision
- 1/2
- Scope
- 2/2
- Quality
- 1/2
Alerts
1 alert, by category
Static scan
- high risk
scripts run by the SKILL.md
scripts/analyze-complexity.py, scripts/detect-smells.py
Original description
Systematic code refactoring based on Martin Fowler's methodology. Use when users ask to refactor code, improve code structure, reduce technical debt, clean up legacy code, eliminate code smells, or improve code maintainability. This skill guides through a phased approach with research, planning, and…
added on Oct 19, 2026 · license MIT