| name | 0.3.3-understand-refused_bequest |
| description | [0.3.3] A subclass using only some inherited methods, suggesting inheritance hierarchy is wrong or composition preferr |
understand-refused_bequest
CALL NUMBER: refactoring_catalog_and_code_smells.refused_bequest
DEFINITION: A subclass using only some inherited methods, suggesting inheritance hierarchy is wrong or composition preferred.
Invoke this skill to understand refused_bequest 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)
CONSUMERS (what needs this)
brittle_signature, liskov_substitution_principle, oop_abusers, replace_inheritance_with_delegation, replace_type_code_with_subclasses
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.)
