0-3-4-understand-dispensables

name	0.3.4-understand-dispensables
description	[0.3.4] Code smells for unnecessary or vestigial elements that could be removed without losing functionality.

understand-dispensables

CALL NUMBER: refactoring_catalog_and_code_smells.dispensables DEFINITION: Code smells for unnecessary or vestigial elements that could be removed without losing functionality.

Invoke this skill to understand dispensables down to its primitives. The RELATIVE ROOT below is the least-fixed-point closure of everything it bundles from — the full import cone, grouped by the lib each prim comes from. Projected from a prover-typed KB (MAP/SWI-Prolog consistency gate): every reference below resolves.

THE RELATIVE ROOT (the import cone, by lib)

from refactoring_catalog_and_code_smells

• commented_out_code (d1): Disabled code left in place, creating confusion and noise; should be deleted and version-controlled instead.
• data_class (d1): A class containing only data fields with accessors and mutators, lacking meaningful behavior.
• dead_code (d1): Code executed but producing no observable effect, or code that can never be executed, increasing maintenance burden.
• lazy_class (d1): A class that does not justify its own existence, having minimal responsibilities and low cohesion.
• speculative_generality (d1): Classes, methods, or parameters added in anticipation of future needs that never materialized.

---

Projected from the refactoring catalog and code smells KB (183 concepts / 128 relations) — consistency-typed by MAP; the facet list after the colon IS the cross-lib dependency web.

(leaf — this is an actual skill.)