Code Simplification

Review code for unnecessary complexity, ungrounded implementation choices, and safe reductions. Preserve behavior and report evidence in maintainability or reduction mode.

1. Maintainability: over-abstraction, generic naming, noisy comments, invented APIs or configuration, stale idioms, dependency creep, and weak tests.
2. Safe reduction: dead or superseded code, orphan files, exact clones, redundant wrappers, inert defensive scaffolding, and comment walls.

Smaller code is not automatically better. A finding needs a concrete maintenance or correctness cost, an invariant, and evidence that the proposed change preserves contracts.

When to use

• Review code or a PR for unnecessary complexity, AI-shaped code, grounded API use, and useful tests.
• Find behavior-preserving reductions before a cleanup change.
• Check a removal or refactor diff for lost behavior, fallbacks, or reachable entry points.

When NOT to use