refactoring-catalog-and-code-smells-module

lpllong_parameter_list: a method or function whose parameter signature exceeds a comfortable cognitive threshold,

coc 001commented_code_element: a syntactic unit of source code that has been rendered inactive by enclosing it in com

bloatersCode smells indicating structures that have grown excessively large and difficult to work with.

brain overloadCognitive complexity where a class or method requires too much context to understand, straining working memory

couplersCode smells indicating excessive or inappropriate dependencies between classes and modules.

dispensablesCode smells for unnecessary or vestigial elements that could be removed without losing functionality.

primitive obsessionUsing primitive types where small objects would provide better semantics, type safety, and expressiveness.

refused bequestA subclass using only some inherited methods, suggesting inheritance hierarchy is wrong or composition preferr

data clumpA group of variables appearing together in multiple locations, indicating a missing class or abstraction.

duplicated codeIdentical or nearly identical code fragments appearing in multiple locations, violating DRY principle.

large classA class containing too many responsibilities, fields, or lines of code indicating violation of single responsi

long methodA method that has grown too large, typically exceeding dozens of lines, making it hard to understand and maint

oop abusersCode smells indicating incorrect or incomplete use of object-oriented constructs and patterns.

speculative generalityClasses, methods, or parameters added in anticipation of future needs that never materialized.

anemic domain modelA domain model consisting of data classes lacking the business logic that should be encapsulated within the ob

boy scout rulePrinciple urging leaving code slightly cleaner than found, enabling incremental refactoring.

change preventersCode smells requiring changes in multiple places when a single responsibility changes.

dead codeCode executed but producing no observable effect, or code that can never be executed, increasing maintenance b

inappropriate intimacyTwo classes with excessive coupling, accessing each other's private details in inappropriate ways.

message chainA series of chained method calls like a.getB().getC().getD(), creating tight coupling across the chain.