What problem does it solve? Code reviews often focus on correctness while ignoring accumulated complexity: reinvented standard library functions, unnecessary dependencies, speculative abstractions, and dead flexibility. This Skill performs a review pass dedicated exclusively to finding what can be deleted or shrunk, keeping diffs lean. ## Core Features & Use Cases - Complexity-Only Review: Hunts over-engineering with five tagged finding types: delete, stdlib, native, yagni, and shrink, each with a concrete replacement suggestion. - One-Line Findings: Outputs terse findings in the format L<line>: <tag> <what>. <replacement>., ending with a net line-reduction score. - Clear Boundaries: Explicitly excludes correctness, security, and performance issues, routing them to a normal review pass, and never flags minimal smoke tests as bloat. - Use Case: After writing a pull request, ask for an over-engineering review to discover that a 27-line validator class can be replaced by a one-line check, or that moment.js can be swapped for Intl.DateTimeFormat with zero dependencies. ## Quick Start Review this diff for over-engineering and tell me what we can delete or simplify.