refactoring
Installation
SKILL.md
Refactoring
Refactoring changes the structure of code and keeps its behavior. One step does little; a sequence of small steps transforms the code, and each step is easy to check. For removing AI slop (narrating comments, bloated names, needless wrappers), use the anti-slop-code skill; this one is about reshaping working code.
Apply only the routes and checks for the selected job. Read a linked skill's named file from its installed folder when available, or from the linked source. Report an unavailable required reference instead of inventing it. [skill-authoring, DISTRIBUTION.md#composing-skills]
| The job | Read |
|---|---|
| Expected failures as typed values instead of exceptions | ERRORS.md |
| Pure calculations, immutable updates, composable rules | FUNCTIONAL.md |
| Design principles as moves: injection and the composition root, strategy, null object, decorator, composite, state, command, memento, Liskov, interface segregation, CQS, Demeter, typestate, deleting speculative layers | DESIGN.md |
| Dependency direction: ports owned by the core, configuration as a port, layer skips, driving vs driven adapters, breaking cycles with a kernel leaf and published ports | DEPENDENCIES.md |
| Deep module interfaces, deletion test, leverage and locality, dependency seams and alternative designs | DEEP-MODULES.md |
| Duplication evidence with jscpd, Deslop and truffler, safe extraction, clone comparison and migration candidates | DUPLICATION.md |
| Dependency usage across imports, configuration and external consumers; measured upgrade/removal decisions | DEPENDENCY-AUDIT.md |