reorganize

Code File Reorganization

Restructure the specified code files: rearrange module layout, reorder logically, extract shared logic, remove redundancy, add section separators and comments. Must not change any functionality or logic.

Target Scope

$ARGUMENTS specifies the target:

• File path: /reorganize src/engine.go — reorganize a single file
• Directory path: /reorganize src/core/ — reorganize all code files in the directory
• diff: /reorganize diff — reorganize all uncommitted files (via git diff --name-only --diff-filter=d HEAD)

If no argument is provided, prompt the user to specify a target.

Execution Flow

Step 1: Determine File List

Resolve the file list from $ARGUMENTS. For directories, recursively collect all code files (excluding vendor, node_modules, generated files, etc.). For diff, collect all uncommitted modified files (staged + unstaged).

Output:

REORGANIZE
  Target:    {file/dir/diff}
  Files:     {N} files
  {file list}

Step 2: Analyze and Reorganize Each File

Process files one at a time. Complete each file before moving to the next.

2.1 Read and Analyze Current Structure

Read the entire file and analyze:

• All type definitions, constants, variables, functions/methods present
• Dependencies and relationships between sections
• Duplicate or reusable logic patterns within this file
• Whether the file couples multiple unrelated functional modules

2.2 Decide Whether to Split the File

Split into multiple files when the file couples multiple clearly distinct functional modules, making it hard to read and maintain:

• The decision is based on module coupling, not line count
• Each resulting file should have focused, single responsibility

When splitting:

• Name new files clearly to reflect their purpose (e.g., engine.go -> engine.go + engine_strategies.go + engine_signals.go)
• Keep the same package/module, ensure compilation passes
• Place shared type definitions in the most logical file, or a separate types file