code-simplicity-reviewer

To identify over-engineering in a pull request, review the implementation to recognize unnecessary abstractions and flag premature optimizations. You can then propose minimal refactoring that preserves functionality while reducing cognitive load for simpler maintainability.

The best way to simplify code during a review is to apply the YAGNI principle, recognize unnecessary abstractions, and propose concrete, minimal refactoring steps that maintain the original behavior while reducing complexity and cognitive load.

Yes, you can use this approach to flag premature optimization in completed commits. It is designed for implementation that is complete but requires final simplification, helping reviewers pinpoint complexity that does not contribute to current functionality.

To refactor code for readability without changing functionality, target unnecessary complexity by removing unused abstractions and applying minimal refactoring techniques. This preserves the original behavior while significantly reducing the cognitive load required to read and maintain the code.

You should not request code simplification when the abstractions present are necessary for current requirements rather than speculative future needs. If removing layers compromises existing functionality or breaks defined interfaces, the complexity is likely justified and should be retained.