code-yeongyu/oh-my-openagent/refactor

export const REFACTOR_TEMPLATE = `# Intelligent Refactor Command

Usage

\\\` /refactor <refactoring-target> [--scope=<file|module|project>] [--strategy=<safe|aggressive>]

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 these todos with the session's todo tool (all pending):

\\\`

• phase-1: PHASE 1: Codebase Analysis - launch parallel explore agents
• phase-2: PHASE 2: Build Codemap - map dependencies and impact zones
• phase-3: PHASE 3: Test Assessment - analyze test coverage and verification strategy
• phase-4: PHASE 4: Plan Generation - invoke Plan agent for detailed refactoring plan
• phase-5: PHASE 5: Execute Refactoring - step-by-step with continuous verification
• phase-6: PHASE 6: Final Verification - full test suite and regression check

\\\`

PHASE 1: CODEBASE ANALYSIS (PARALLEL EXPLORATION)

Mark phase-1 as in_progress.

1.1: Launch Parallel Explore Agents (BACKGROUND)

Fire ALL of these simultaneously using \call_omo_agent\:

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

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

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

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

// Agent 5: Architecture context call_omo_agent( subagent_type="explore", run_in_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) lsp_goto_definition(filePath, line, character) // Where is it defined?

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

// Get file structure lsp_symbols(filePath, scope="document") // Hierarchical outline lsp_symbols(filePath, scope="workspace", 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 — run this from the ast-grep skill's directory; this skill ships no scripts/ python3 scripts/ast_grep_helper.py search 'function $NAME($$$) { $$$ }' src/ --lang ts

Preview refactoring first

sg --pattern '[old_pattern]' --rewrite '[new_pattern]' --lang ts src/ \\\`

Grep for Text Patterns:

\\\ grep(pattern="[search_term]", path="src/") // narrow to *.ts with the grep tool's file-filter parameter \\\

1.3: Collect Background Results

\\\ background_output(task_id="[agent_1_id]") background_output(task_id="[agent_2_id]") ... \\\

Mark phase-1 as completed after all results collected.

PHASE 2: BUILD CODEMAP (DEPENDENCY MAPPING)

Mark phase-2 as in_progress.

2.1: Construct Definitive Codemap

Based on Phase 1 results, build:

\\\`

CODEMAP: [TARGET]

Core Files (Direct Impact)

• \path/to/file.ts:L10-L50\ - Primary definition
• \path/to/file2.ts:L25\ - Key usage

Dependency Graph

\\\ [TARGET] ├── imports from: │ ├── module-a (types) │ └── module-b (utils) ├── imported by: │ ├── consumer-1.ts │ ├── consumer-2.ts │ └── consumer-3.ts └── used by: ├── handler.ts (direct call) └── service.ts (dependency injection) \\\

Impact Zones

Established Patterns

• Pattern A: [description] - used in N places
• Pattern B: [description] - established convention

\\\`

2.2: Identify Refactoring Constraints

Based on codemap:

• MUST follow: [existing patterns identified]
• MUST NOT break: [critical dependencies]
• Safe to change: [isolated code zones]
• Requires migration: [breaking changes impact]

Mark phase-2 as completed.

PHASE 3: TEST ASSESSMENT (VERIFICATION STRATEGY)

Mark phase-3 as in_progress.

3.1: Detect Test Infrastructure

\\\`bash

Check for test commands

cat package.json | jq '.scripts | keys[] | select(test("test"))'

Or for Python

ls -la pytest.ini pyproject.toml setup.cfg

Or for Go

ls -la *_test.go \\\`

3.2: Analyze Test Coverage

\\\` // Find all tests related to target call_omo_agent( subagent_type="explore", run_in_background=false, // Need this synchronously prompt="Analyze test coverage for [TARGET]:

1. Which test files cover this code?
2. What test cases exist?
3. Are there integration tests?
4. What edge cases are tested?
5. Estimated coverage percentage?"

) \\\`

3.3: Determine Verification Strategy

Based on test analysis:

If coverage is LOW or NONE, ask user:

\\\` Test coverage for [TARGET] is [LEVEL].

Risk Assessment: Refactoring without adequate tests is dangerous.

Options:

1. Add tests first, then refactor (RECOMMENDED)
2. Proceed with extra caution, manual verification required
3. Abort refactoring

Which approach do you prefer? \\\`

3.4: Document Verification Plan

\\\`

VERIFICATION PLAN

Test Commands

• Unit: \bun test\ / \npm test\ / \pytest\ / etc.
• Integration: [command if exists]
• Type check: \tsc --noEmit\ / \pyright\ / etc.
• Lint: [project's linter command, the one Phase 6.3 runs]

Baseline (before any change)

• Pass counts: [X/Y passing per test command above]
• lsp_diagnostics: [pre-existing diagnostics recorded in Phase 1.2]

Verification Checkpoints

After each refactoring step:

1. lsp_diagnostics → zero new errors
2. Run test command → all pass
3. Type check → clean

Regression Indicators

• [Specific test that must pass]
• [Behavior that must be preserved]
• [API contract that must not change]

\\\`

Mark phase-3 as completed.

PHASE 4: PLAN GENERATION (PLAN AGENT)

Mark phase-4 as in_progress.

4.1: Invoke Plan Agent

\\\` Task( subagent_type="plan", prompt="Create a detailed refactoring plan:

## Refactoring Goal [User's original request]

## Codemap (from Phase 2) [Insert codemap here]

## Test Coverage (from Phase 3) [Insert verification plan here]

## Constraints

• MUST follow existing patterns: [list]
• MUST NOT break: [critical paths]
• MUST run tests after each step

## Requirements

1. Break down into atomic refactoring steps
2. Each step must be independently verifiable
3. Order steps by dependency (what must happen first)
4. Specify exact files and line ranges for each step
5. Include rollback strategy for each step
6. Define commit checkpoints"

) \\\`

4.2: Review and Validate Plan

After receiving plan from Plan agent:

1. Verify completeness: All identified files addressed?
2. Verify safety: Each step reversible?
3. Verify order: Dependencies respected?
4. Verify verification: Test commands specified?

4.3: Register Detailed Todos

Convert Plan agent output into granular todos with the session's todo tool (each step from the plan becomes a todo, followed by its verify todo):

\\\`

• refactor-1: Step 1: [description]
• verify-1: Verify Step 1: run tests
• refactor-2: Step 2: [description]
• verify-2: Verify Step 2: run tests
• ... continue for all steps

\\\`

Mark phase-4 as completed.

PHASE 5: EXECUTE REFACTORING (DETERMINISTIC EXECUTION)

Mark phase-5 as in_progress.

5.1: Execution Protocol

For EACH refactoring step:

Pre-Step

1. Mark step todo as \in_progress\
2. Read current file state
3. Verify lsp_diagnostics is baseline

Execute Step

Use appropriate tool:

For Symbol Renames: \\\typescript lsp_prepare_rename(filePath, line, character) // Validate rename is possible lsp_rename(filePath, line, character, newName) // Execute rename \\\

For Pattern Transformations: \\\`bash // Preview first sg --pattern '[pattern]' --rewrite '[rewrite]' --lang ts path/to/file.ts

// If preview looks good, execute (from the ast-grep skill's directory) python3 scripts/ast_grep_helper.py replace '[pattern]' '[rewrite]' path/to/file.ts --lang ts --apply \\\`

For Structural Changes: \\\typescript // Use Edit tool for precise changes edit(filePath, oldString, newString) \\\

Post-Step Verification (MANDATORY)

\\\`typescript // 1. Check diagnostics lsp_diagnostics(filePath) // Must be clean or same as baseline