Lean Review

Review code with one question in mind: does each piece of structure earn its keep right now?

This skill is for conservative simplification review, not minimalism for its own sake. Do not flatten or remove structure that materially improves readability, naming, local reasoning, or ownership boundaries. A single-use helper, nested directory, or small composed object can be worth keeping when it makes the code easier to understand.

Workflow

1. Anchor the review in the real code.

• Read the changed files, nearby interfaces, and affected tests or docs.
• Distinguish between:
  • necessary structure serving current behavior
  • readability-oriented structure that pays for itself now
  • speculative or low-value structure added mostly for hypothetical future use