maintainability-review
Maintainability Review
Run a two-phase, evidence-led review. Preserve behavior and public boundaries unless correctness, measured performance, or a seriously misleading name provides strong contrary evidence.
Read the canonical engineering house style and the review rubric before auditing or changing code. The engineering standard owns durable code rules; this skill owns the review procedure. Do not restate the standard in findings, plans, or package documentation.
When a review includes complexity ceilings, metric-driven refactoring, or type-erasure/inference concerns, also read the complexity and type-integrity guide. It defines the repository thresholds, measurement limits, anti-gaming rules, and current evidence-led refactor candidates.
When a review adds, removes, consolidates, or evaluates tests, also read the test portfolio guide. It defines how to assign one authoritative test to each product invariant without deleting focused trust-boundary, failure, type-contract, or hot-path evidence.