Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ciembor/refactoring-guru
Apply Refactoring.Guru-inspired rules when diagnosing code smells, choosing refactoring techniques, and stopping cleanup before uncontrolled redesign.
Passed 22 of 24 test cases with the skill, and 21 of 24 without it.
1 fixed21 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
Adding a new user permission role requires modifying 14 separate files spanning controllers, views, database mappers, and audit logs. A team lead suggests using a search-and-replace script across those 14 files whenever permissions change. What code smell does this represent, and how should it be refactored?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies the code smell as Shotgun Surgery. | Passed | Passed |
| Recommends Move Method to consolidate the scattered permission logic into a single class. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill when a task involves diagnosing smells, choosing targeted refactoring treatments, preserving behavior, applying a refactoring catalog, or avoiding uncontrolled redesign.
Before making design or code decisions, read and apply refactoring-guru.mini.md. Use refactoring-guru.md only as a deeper reference when the mini rules are not enough for the current refactoring tradeoff.
test cases passed, vs 21 / 24 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.