CompileScope

The problem. As a Unity project grows, a small script change can trigger a recompile of a much larger fraction of the project than expected, and domain reload time climbs without an obvious cause. Diagnosing which Assembly Definition boundary is actually responsible usually means manually tracing .asmdef references by hand.

How CompileScope addresses it. CompileScope reads your project's existing Assembly Definition files and Unity's own compilation and domain reload events, builds a dependency graph in the background, and turns it into a ranked, actionable list of what to fix — without requiring any change to your code or .asmdef files to analyze it.

What it does:

Discovers every assembly in your project and builds a full dependency graph from real .asmdef references, with a three-pane relationship viewer for any assembly you select.

Calculates a cascade score for every assembly — the fraction of the project that recompiles when that assembly changes — so you can see which assembly is actually worth splitting, not just which one is slow.

Generates ranked recommendations from five built-in rules: orphan scripts with no assembly boundary, editor code in a non-editor assembly, high-cascade utility assemblies, test assemblies with heavy production dependencies, and near-circular dependency candidates.

Tracks compilation and domain reload history automatically in the background, so you can confirm a restructuring actually helped rather than guessing.

Includes a synthetic demo dataset, so you can explore every tab before pointing it at a real project.

Documentation

Discord

Report issues