Menu
Find worthwhile architectural refactors, decide one with the user, and turn it into a plan.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/RobinBoers/dotfiles --skill refactorThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Based on SOC occupation classification
Showing SKILL.md
| name | refactor |
| description | Find worthwhile architectural refactors, decide one with the user, and turn it into a plan. |
| disable-model-invocation | true |
Find architectural friction and propose deepening opportunities: changes that put more useful behavior behind smaller interfaces.
Use the scope or pain point the user names. Otherwise inspect enough git history to find recent or recurring change hotspots before widening the search. Refactoring pays where future changes are likely. Do not scan the entire repository by habit.
Read repository instructions, .claude/domain.md, relevant plans and decisions, then the code and tests in that area. Existing decisions are constraints, not commandments: reopen one only when current friction justifies it.
Use /codebase-design and follow friction rather than a rigid smell checklist. Look for:
Apply the deletion test to suspected shallow modules. Classify dependencies before suggesting a new seam. Reject speculative abstractions and changes that merely add a layer.
Rank a small set in chat. For each candidate include:
Show a compact before/after diagram when relationships matter. Recommend one candidate and explain why it beats the others.
Do not design the final interface yet. Ask which candidate the user wants to explore.
For the chosen candidate:
/interview over constraints, module responsibility, interface, seam, adapters, migration, compatibility, tests, rollout, and rollback where relevant./codebase-design's design-it-twice process when the interface is expensive or uncertain./domain-modeling when naming exposes a real domain ambiguity..claude/decisions, name the conflict and why reopening it may be justified.Save agreed non-trivial work to .claude/plans/<name>.md, with ordered migration and verification steps. Do not implement unless asked separately.