This skill loads a compact rule set inspired by the Refactoring.Guru smell and technique catalog. It tells a coding agent to diagnose a smell first, name its cost and the verification path, then apply the smallest technique that treats it.
It groups smells into bloaters, object-orientation abusers, change preventers, dispensables and couplers, and gives pre-checks for extraction, data reorganization and generalization.
What You Get
- A mini rule set with decision rules, trigger rules and a closing checklist for smell-driven refactoring
- A nano version for tight context budgets and a full version with the longer catalog notes
- A skill description that makes the agent load the rules for smell diagnosis and technique choice
Common Use Cases
- Diagnosing a long method and picking extract method or replace temp with query
- Removing a middle man or hiding a delegate to cut navigation through object chains
- Deleting dead code after checking reflection, serialization and plugin use
- Applying the rule of three before removing duplication
What Makes It Unique
It organises the work by smell category and names the technique to try for each trigger. It also warns when a mechanical treatment is the wrong call, such as a simple conditional or a clear duplicate, and asks that untreated smells are recorded and not hidden. The Fowler-based refactoring set in the repository is organised around the sequence of the change.
Under The Hood
The skill is a SKILL.md with a name and description, plus Markdown files holding the mini, nano and full versions of the rules. The SKILL.md tells the agent to read the mini file before design or code decisions and the full file only for harder tradeoffs. It contains no scripts. It does not fetch web pages, call APIs, run commands or write files; the agent only reads the rule text.