module-health

Module health assessment evaluates your template's module structure by calculating scores based on size, property distribution, documentation, and organization. Run the health check on code organized under source/MODULE with classes.edn and properties.edn files to identify bloated, orphaned, or imbalanced modules and receive actionable refactoring recommendations.

A module health score measures balance, cohesion, dependencies, and completeness across your template's modules. The score reflects module size distribution, property coverage, documentation quality, and architectural clarity, helping you spot maintenance issues before they compound.

Yes. Module health detection identifies oversized or poorly organized modules like misc/ and generates reorganization plans. The output suggests how to split bloated modules into focused domains—such as medical/ or financial/—with specific refactoring steps.

Your Logseq template must be organized with a source/MODULE directory structure containing classes.edn and properties.edn files in each module. This structure enables the health assessment to calculate per-module scoring, detect imbalance, and provide remediation guidance.

A module health report provides per-module health scores, size balance ratios, documentation completeness metrics, and a structured breakdown of findings. It delivers actionable remediation guidance identifying which modules need splitting, merging, or reorganization.

By exposing imbalanced dependencies, undocumented modules, and architectural bloat, module health assessment enables proactive refactoring. Fixing identified issues—splitting large modules and improving cohesion—reduces maintenance friction and keeps your template scalable as it grows.