refactor skill

export const REFACTOR_TEMPLATE = # Intelligent Refactor Command

Usage

\\\ /refactor [--scope=] [--strategy=]

Arguments: refactoring-target: What to refactor. Can be:

• File path: src/auth/handler.ts
• Symbol name: "AuthService class"
• Pattern: "all functions using deprecated API"
• Description: "extract validation logic into separate module"

Options: --scope: Refactoring scope (default: module)

• file: Single file only
• module: Module/directory scope
• project: Entire codebase

--strategy: Risk tolerance (default: safe)

\\\

• safe: Conservative, maximum test coverage required
• aggressive: Allow broader changes with adequate coverage

What This Command Does

Performs intelligent, deterministic refactoring with full codebase awareness. Unlike blind search-and-replace, this command:

1. Understands your intent - Analyzes what you actually want to achieve
2. Maps the codebase - Builds a definitive codemap before touching anything
3. Assesses risk - Evaluates test coverage and determines verification strategy
4. Plans meticulously - Creates a detailed plan with Plan agent
5. Executes precisely - Step-by-step refactoring with LSP and AST-grep
6. Verifies constantly - Runs tests after each change to ensure zero regression

PHASE 0: INTENT GATE (MANDATORY FIRST STEP)

BEFORE ANY ACTION, classify and validate the request.

Step 0.1: Parse Request Type

Step 0.2: Validate Understanding

Before proceeding, confirm:

• [ ] Target is clearly identified
• [ ] Desired outcome is understood
• [ ] Scope is defined (file/module/project)
• [ ] Success criteria can be articulated

If ANY of above is unclear, ASK CLARIFYING QUESTION:

\\\ I want to make sure I understand the refactoring goal correctly.

What I understood: [interpretation] What I'm unsure about: [specific ambiguity]

Options I see:

1. [Option A] - [implications]
2. [Option B] - [implications]

My recommendation: [suggestion with reasoning]

Should I proceed with [recommendation], or would you prefer differently? \\\

Step 0.3: Create Initial Todos

IMMEDIATELY after understanding the request, create todos:

\\\ TodoWrite([ {"id": "phase-1", "content": "PHASE 1: Codebase Analysis - launch parallel explore agents", "status": "pending", "priority": "high"}, {"id": "phase-2", "content": "PHASE 2: Build Codemap - map dependencies and impact zones", "status": "pending", "priority": "high"}, {"id": "phase-3", "content": "PHASE 3: Test Assessment - analyze test coverage and verification strategy", "status": "pending", "priority": "high"}, {"id": "phase-4", "content": "PHASE 4: Plan Generation - invoke Plan agent for detailed refactoring plan", "status": "pending", "priority": "high"}, {"id": "phase-5", "content": "PHASE 5: Execute Refactoring - step-by-step with continuous verification", "status": "pending", "priority": "high"}, {"id": "phase-6", "content": "PHASE 6: Final Verification - full test suite and regression check", "status": "pending", "priority": "high"} ]) \\\

PHASE 1: CODEBASE ANALYSIS (PARALLEL EXPLORATION)

Mark phase-1 as inprogress.**

1.1: Launch Parallel Explore Agents (BACKGROUND)

Fire ALL of these simultaneously using \callomoagent\:

\\\ // Agent 1: Find the refactoring target callomoagent( subagenttype="explore", runin_background=true, prompt="Find all occurrences and definitions of [TARGET]. Report: file paths, line numbers, usage patterns." )

// Agent 2: Find related code callomoagent( subagenttype="explore", runin_background=true, prompt="Find all code that imports, uses, or depends on [TARGET]. Report: dependency chains, import graphs." )

// Agent 3: Find similar patterns callomoagent( subagenttype="explore", runin_background=true, prompt="Find similar code patterns to [TARGET] in the codebase. Report: analogous implementations, established conventions." )

// Agent 4: Find tests callomoagent( subagenttype="explore", runin_background=true, prompt="Find all test files related to [TARGET]. Report: test file paths, test case names, coverage indicators." )

// Agent 5: Architecture context callomoagent( subagenttype="explore", runin_background=true, prompt="Find architectural patterns and module organization around [TARGET]. Report: module boundaries, layer structure, design patterns in use." ) \\\

1.2: Direct Tool Exploration (WHILE AGENTS RUN)

While background agents are running, use direct tools:

LSP Tools for Precise Analysis:

\\\typescript // Find definition(s) LspGotoDefinition(filePath, line, character) // Where is it defined?

// Find ALL usages across workspace LspFindReferences(filePath, line, character, includeDeclaration=true)

// Get file structure LspDocumentSymbols(filePath) // Hierarchical outline LspWorkspaceSymbols(filePath, query="[target_symbol]") // Search by name

// Get current diagnostics lsp_diagnostics(filePath) // Errors, warnings before we start \\\

AST-Grep Skill for Pattern Analysis:

\\\bash // Find structural patterns python3 scripts/astgrephelper.py search 'function $NAME($$$) { $$$ }' --lang ts src/

Preview refactoring first

sg --pattern '[oldpattern]' --rewrite '[newpattern]' --lang ts src/ \\\

Grep for Text Patterns:

\\\ grep(pattern="[searchterm]", path="src/", include=".ts") \\\

1.3: Collect Background Results

\\\ backgroundoutput(taskid="[agent1id]") backgroundoutput(taskid="[agent2id]") ... \\\

Mark phase-1 as completed after all results collected.

PHASE 2: BUILD CODEMAP (DEPENDENCY MAPPING)

Mark phase-2 as inprogress.**

2.1: Construct Definitive Codemap

Based on Phase 1 results, build:

\\\

CODEMAP: [TARGET]