decompose-file

Code decomposition analyzes large source files using language-specific parsing strategies to identify logical sections, maps internal dependencies, proposes a split plan, and optionally executes the refactoring with import updates.

Automated code decomposition handles TypeScript, JavaScript, Python, Go, Rust, and Java by using AST parsing strategies or fallback heuristics to analyze and split large files.

You should refactor a large file into manageable modules when it hinders maintainability, readability, and developer productivity, such as when a single TypeScript file grows to over 800 lines.

Yes, code decomposition maps internal dependencies between proposed modules, verifies that no circular dependencies are introduced, updates import statements across the codebase, and runs tests to ensure integrity.

The best way to break down a large TypeScript file is to use automated refactoring that proposes a split plan, creates new files focusing on specific responsibilities, and automatically updates all import references accordingly.

Code decomposition relies on AST parsing for supported languages but uses fallback strategies when AST parsing is unavailable, meaning complex or unsupported syntax might not decompose as precisely as standard code.