Find Best Refactor

Overview

Inspect the repo from first principles, generate multiple plausible refactor candidates, and pick the one with the best leverage relative to cost and risk.

Do not ask the user to choose among options. Make the call, explain it, and write an implementation-ready ExecPlan.

Mindset

Approach this like a principal engineer finding the one refactor that most improves the codebase per unit of churn.

You are not limited to one refactor shape. The winning move might be:

• consolidation of duplicate abstractions or parallel modules
• extraction of domain logic from infrastructure-heavy flows
• removal of a dead or thin abstraction layer
• extraction of an implicit state machine or policy engine
• merge of duplicate orchestration paths
• simplification of a leaky interface that forces callers to know too much