clean-code-size

To identify oversized files in a monolithic codebase for refactoring, scan the repository using language-specific non-blank line thresholds. This triage process flags large source files as candidates for structural decomposition and generates architect-led module split proposals.

The best way to plan safe module splits for large source files is to generate an architect-led module breakdown. This defines specific module responsibilities, dependency directions, and a safe migration order, routing implementation to downstream engineering skills.

Code size triage works with Python, JavaScript, TypeScript, C#, Rust, and Go projects. It automatically detects file languages and applies appropriate size thresholds, with support for custom threshold overrides to accurately flag files for structural decomposition.

During a code audit size triage, legitimate large files are filtered out using false positive filtering. This exempts generated code, constant registries, test fixtures, and schema declarations from receiving unnecessary module split proposals.

You should run an architecture review for module decomposition when your repository feels monolithic and files become too large to review effectively. It serves as a size-focused triage step before running refactoring work or assigning tasks to language-specific engineers.