module-size-discipline

Solid

Use when planning tasks that touch big source files, when an edit would push a file past the module-size ceiling, when the pre-commit module-size ratchet warns or blocks, or when generating policies/module-size-baseline.txt. Operationalizes FR-25 — module-size ratchet (ceiling default 800; over-ceiling files may shrink, never grow; extraction along a responsibility seam is in-scope, not scope creep). Do NOT use for docs/markdown size (FR-23 owns docs), to force decomposition of an existing monolith (that is its own explicit ticket), or to judge split quality by regex (seam-vs-mechanical is semantic — code-review owns it).

Code & Development 9 stars 0 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
33
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Module-Size Discipline (FR-25) ## Purpose Stop source files from accreting into monoliths nobody (human or agent) can load in one pass. Source in a Flow workflow is AI-read (FR-22/FR-24 audience principle): a 19k-line file forces slice-reads on every future session. Monoliths are the integral of N individually-reasonable diffs — no single diff is ever flagged — so the framework gates the accumulating dimension deterministically (line count is objective, unlike FR-22/FR-23 semantics) and steers extraction at plan- and write-time. ## The ratchet (deterministic gate) Config: `policies/module-size.yml` (`ceiling` default 800 · `source_globs` · `exempt_globs` · `baseline_file` · `enforcement` · gitignored `module-size.local.yml` override). Engine: `hooks/shared/module_size.py`, wrapper `hooks/local/check-module-size.sh`, wired into `hooks/git/pre-commit`. | Case | Verdict | |---|---| | Gated file NOT in baseline, lines ≤ ceiling | pass | | NOT in baseline, **NEW** over ceiling (crosses the ceiling in this change) | **BLOCK** — extract, or adopt (`--write-baseline`) | | NOT in baseline, **PRE-EXISTING** over ceiling (over ceiling at HEAD), touched/shrunk in a change gate (`--staged`/`--worktree`, not growing) | pass — the refactor path (delta-aware adoption grace) | | NOT in baseline, **PRE-EXISTING** over ceiling, **GROWN** | **BLOCK** — a monolith may be touched/shrunk, never grown | | Any over-ceiling not-baselined file under `--all` (audit) | **reported** (absolute; no H...

Details

Author
fusebase-dev
Repository
fusebase-dev/fusebase-flow
Created
4 months ago
Last Updated
1 weeks ago
Language
Shell
License
MIT

Bundled in these plugins

fusebase-flow

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

python-guidelines

Make the design calls no linter can check — where an oversized file splits, whether a name or docstring carries meaning, whether an abstraction earns its keep, when a suppression is legitimate, and how to satisfy a size or complexity ratchet without gaming it. Use when a size or complexity gate has just failed, before adding a noqa or nosec, when deciding what to raise and what to catch, or when shared state is reached from more than one concurrent lane.

0 Updated today
niksavis
AI & Automation Listed

decomposition

Decompose a file that has grown over the size ceiling into focused sibling files — extracting at cognitive seams (hooks, sub-components, pure helpers, types), in the right order, behind a user-approved plan, with post-extraction verification. Invoke when a file-size check warns or a file has become too large to navigate. Refuses on auto-generated, snapshot, and fixture files.

1 Updated 2 weeks ago
vindm
AI & Automation Listed

extract-module

Split an overgrown file into cohesive, well-bounded modules — find the natural seams, design each new module's public interface before moving a line, then relocate one unit at a time keeping tests green. Use when a file has grown too large, mixes unrelated responsibilities, or every change to it forces unrelated diffs and merge conflicts.

1 Updated 2 weeks ago
imtiazrayhan