pragmatism-audit

Code complexity review identifies over-engineered sections by inspecting recent changes against project scale. It proposes efficient refactorings that reduce unnecessary complexity while maintaining core functionality, ensuring clean and maintainable codebases after architectural decisions and feature implementation.

Run a code complexity audit after implementing features or making architectural decisions to catch over-engineering early. This inspection identifies excessive complexity in recent changes, proposing refactoring that simplifies code design and maintains clean, maintainable codebases without sacrificing functionality.

Refactor over-engineered code by reviewing source code for excessive complexity relative to project scale, then proposing efficient designs that maintain functionality. This approach simplifies code without sacrificing features, ensuring the refactored codebase remains clean and maintainable while delivering the same core results.

Yes, this code review approach evaluates complexity relative to project scale, making it applicable across various project sizes. It inspects recent code changes to determine if design complexity matches actual needs, proposing refactoring where excessive patterns are identified, ensuring appropriate design for any scale.

No, this complexity review requires no specific dependencies or frameworks. It operates as a standalone skill with scripts and references, directly reviewing source code to identify excessive complexity and propose refactoring for more efficient code design, making it applicable across any codebase without setup.

Your codebase feels over-engineered when recent changes introduce excessive complexity not warranted by project scale. A code complexity review inspects these changes, identifies unnecessary design patterns, and proposes refactoring to simplify the code while maintaining core functionality, ensuring efficient and maintainable design.