/rota-refactor
Review the architecture and file refactor issues; –map drafts the map.
When to use
Use on “review the architecture”, “find refactoring opportunities”, “deepen modules”, “map the repo”, “refresh the project map” (–map), or scoped to one area (“/rota-refactor internal/cli”).
Reach for another skill when
- the refactor is already an issue and ready to build:
/rota-work - you are planning product milestones, not code structure:
/rota-vision
Strong: split cmd dispatch from flag parsing (deletion test: parsing has one caller). Worth exploring: second adapter for the config store. Filed #71 and #72 as `refactor` issues with `## Acceptance`; skipped 1 duplicate. No code changed.
- one
refactor-labelled issue per candidate - no code changes unless you pass –fix
Flags and modes
--fix- implement the candidates you pick (parallel workers, verification, one commit)
--designs- draft competing interfaces for structural candidates
--interactive- choose which candidates to file
--map- write the
.rota/map/subsystem files, then runrota map index
Details
Architecture review. Explores the codebase (or one area, /rota-refactor internal/cli) for friction using one vocabulary (module, interface, depth, seam, adapter, leverage, locality) and a few heuristics (the deletion test, the interface as the test surface, one adapter is a hypothetical seam). It reads the glossary, knowledge and decisions first, ranks candidates Strong / Worth exploring / Speculative, and files each as a refactor-labelled issue with a ## Acceptance section, deduped against open and closed issues. It changes no code by default.
Flags: --fix implements the candidates you pick (parallel workers, verification, one commit; refactor.confirmBeforeExecute gates it), --designs drafts competing interfaces for structural candidates, --interactive lets you choose which to file. Several workers can each review one area in a round.