review-simplicity

To spot over-engineering in your codebase, audit your code for speculative generality, YAGNI violations, and premature abstractions. This read-only analysis evaluates specific files or directory diffs to surface anti-patterns and reduce cognitive load.

Premature abstraction occurs when code is built for speculative future needs rather than current requirements, negatively impacting maintainability. Structured complexity assessment identifies these YAGNI violations, guiding engineers toward simpler, maintainable code without altering functionality.

Yes, you can review diffs against origin/main to check for YAGNI violations. This scope-aware analysis focuses the complexity assessment exclusively on relevant changes, delivering actionable simplification recommendations for the newly written code.

You can analyze over-parameterized interfaces without modifying functionality by running a read-only simplification review. This process enforces structured evaluation across context gathering and complexity assessment to provide actionable simplification recommendations.

Yes, this code review process works on explicitly specified files and directories. By providing the specific file paths or scope, the analysis enforces structured evaluation to identify unnecessary complexity and over-engineering across the targeted codebase.

You should not expect automated simplification recommendations to modify your functionality. This analysis is strictly read-only, meaning it surfaces anti-patterns and guides engineers toward simpler code structures without directly executing refactoring changes.