refactorkitlisted

# refactorkit The survey you run on a codebase you already have. refactorkit reads the repo, meaning its churn, its module shapes, and its tests, finds where the *structure* is costing you, ranks the candidates against two gates, crowns exactly one, and writes it up as a proposal somebody can argue with. It is a single procedure, optionally scoped to a subtree (`/refactorkit src/payments`). There are no modes: everything it does, it does the same way on every run. ## It proposes, it never edits **refactorkit writes exactly one Markdown file and touches no source code.** No moves, no renames, no extractions, no "small tidy-up while I'm in here." The name says *refactor*; the skill only ever says *where and why*, and the doing belongs to whoever picks the proposal up. That boundary is the whole reason the report can be trusted, because a survey that also edits has already decided, and you're reading a rationalization rather than a recommendation. `Edit` is deliberately absent from this skill's tools. The one file it creates is new, so `Write` covers it. ## When this fires "Where should I refactor this", "what's wrong with this codebase's structure", "find refactoring opportunities", "this code is hard to change", "improve our architecture", "audit the module boundaries", "the seams here are a mess", "/refactorkit". Four boundaries, one line each: - **Not a code review.** A review reads a *diff* for defects in work someone just did. refactorkit reads the *tree* for stru