optimize_codebase

To refactor monolithic files, you analyze the codebase to identify oversized source files and generate a modular split plan that creates new directories, index entry points, and clear module boundaries. This workflow preserves existing behavior while improving maintainability.

Splitting large codebase files safely requires a step-by-step refactor workflow including analysis, plan generation, execution, and verification. This approach creates per-file directories and index entry points to modularize code while strictly preserving existing behavior.

The threshold for identifying monolithic source files is any source file exceeding 2000 lines. Files surpassing this limit are targeted for modularization to improve codebase maintainability and establish a scalable architecture.

Yes, this modularization approach works across multiple languages including HTML, Python, and JavaScript. It detects oversized source files regardless of language and proposes a reusable modular plan with index entry points to improve maintainability.

The best way to improve maintainability in a monolithic codebase is to refactor oversized files into modular component structures. By generating per-file directories and clear module boundaries, the codebase achieves better maintainability and a scalable architecture.

You should avoid breaking down big files if they do not exceed the 2000-line threshold or if the codebase lacks proper verification steps. Modularization is designed for oversized files where preserving behavior can be guaranteed through a structured refactor workflow.