Maintainability Review

Review whether the code is easy to understand, change, and extend against the codebase's existing conventions. Rules that hold regardless of local convention — control flow, constants, indirection, comments — are code-writing's and design-review's.

Scope

1. Naming and organization

• naming consistency across types, constants, functions, and files
• names that describe their content rather than their category, judged in context: a bare data, temp, or result holding something specific is the smell, but the same word is right where it is the domain's own term, a published API name, or an accumulator the function builds and returns — check the spec and the exports before flagging one
• renamed concepts stay aligned across code, tests, docs, and exported identifiers
• constructor and factory naming follows a single project convention
• module and file layout follows the established project structure
• import/export patterns are consistent across the codebase

2. Control flow and state modeling