God file
Part of Code Quality & Syntax, which counts for 20% of the overall score. When this check fires it deducts 8 points from that category, once per scan, no matter how many places it turns up.
What it detects
A single file defining 15+ top-level functions/classes usually needs to be split by responsibility.
Why it matters
A file defining more than 15 top-level functions or classes has become a dumping ground: everything imports it, it shows up in every merge conflict, and nobody can state what it is responsible for. Changes there have the widest blast radius in the codebase.
How to fix it
Group the definitions by theme and move each group into its own module named for that theme (dates.ts, validation.py; avoid grab-bag names like utils2). Keep the original file as a re-export barrel while imports still point at it, then migrate the imports over time.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo