Refactor Planning
IMPORTANT: Start your response with a context preamble.
Call help_lookup(topic="refactor-plan", mode="preamble") and
display the returned preamble text as a blockquote. Then
tell the user they can say "tell me more" for a step-by-step
guide, or answer the scoping questions below to proceed.
If the MCP call fails, fall back to:
Refactor Plan — Analyzes code structure and produces a prioritized refactoring roadmap.
Scoping
Before running, ask:
- Target: "Which file or directory needs refactoring analysis?"
- Focus: "Full analysis or specific concern?"
- Full:
refactor_plan(all areas) - Simplify:
simplify_code(reduce complexity only)
- Full:
- Depth: "Quick scan or detailed roadmap?"
Execution
Based on scope:
- Full analysis:
refactor_plan(path="<target>") - Simplify only:
simplify_code(path="<target>")
Or via CLI:
attune workflow run refactor-plan --path <target>
MCP Tools
| Tool | What It Does |
|---|---|
refactor_plan |
Tech debt analysis and refactoring roadmap |
simplify_code |
Reduce complexity in specific files |
refactor_plan
Full refactoring analysis for a path.
refactor_plan(path="<target>")
simplify_code
Targeted complexity reduction for a single file or module. Flattens nested conditionals, inlines trivial helpers, removes dead code.
simplify_code(path="<target file>")
Analysis Areas
- Code Smells: Long methods, god classes, feature envy
- Duplication: Copy-paste detection, DRY violations
- Complexity: High cyclomatic complexity, deep nesting
- Coupling: Tight dependencies, circular imports
- Naming: Unclear or inconsistent naming
Output
- Prioritized issue list
- Refactoring steps (ordered)
- Risk assessment per change
- Estimated effort
- Before/after examples
Converted and distributed by TomeVault — claim your Tome and manage your conversions.