code-consolidator

To refactor fragmented modules, identify over-separated files and apply consolidation patterns to merge thin wrappers and single-use layers. This reduces indirection and cognitive load while preserving behavior by safely updating imports across your codebase.

The best way to consolidate scattered configurations is to unify fragmented config files into a single cohesive configuration strategy. This involves recognizing code smells related to distributed settings and merging them to improve maintainability and readability.

To inline trivial abstractions safely, collapse single-use layers and apply consolidation patterns while updating imports to keep behavior intact. This process simplifies navigation and reduces unnecessary indirection within your architecture.

You should preserve boundaries instead of merging over-separated code when collapsing the abstraction would increase complexity or break architectural intent. Evaluate code smells to balance whether merging related files genuinely improves maintainability or just hides important separation of concerns.

The maximum file size limit when merging scattered code is 200 lines per merged unit. This constraint ensures that consolidating over-separated modules and collapsing layers improves readability without creating overly large and complex files.

Your codebase has too many wrappers and scattered configs due to over-separation, a code smell where abstractions are fragmented across layers. Consolidating these related files and inlining trivial abstractions reduces cognitive load and simplifies navigation.