heathen

God file detection scans JavaScript and TypeScript repositories to rank oversized components and modules that mix multiple responsibilities. It identifies files combining UI rendering, data shaping, and business logic to produce a prioritized candidate list for safe decomposition.

Splitting large React components safely requires an evidence-first decomposition order that prioritizes testable extractions like hooks and subcomponents. This approach preserves public interfaces where possible and minimizes breaking changes by guiding sequential extractions with verification steps.

Duplicate code block detection scans JavaScript and TypeScript files to find repeated logic across modules. It identifies recurring code patterns to prioritize safe extractions, helping reduce code brittleness while preserving behavior during refactoring or architectural restructuring tasks.

This refactoring approach works with both JavaScript and TypeScript repositories, applying to script decomposition alongside React component simplification and module responsibility splitting. It evaluates candidates and produces split sequences for various file types mixing oversized responsibilities.

You should avoid splitting god files when the oversized module lacks test coverage or when decomposition would expose internal implementation details critical to the public interface. Safe decomposition requires prioritizing testable extractions and verifying behavior preservation after each sequential step.

Sprawling React page components cause brittleness because they mix rendering, data shaping, effects management, and business logic within a single file. Extracting helpers, hooks, and subcomponents in a testable sequence reduces this brittleness while preserving application behavior.