arib-dev-lean

You can identify over-engineering by analyzing source code modules and git diffs to apply a YAGNI-based complexity ladder, which flags unnecessary abstractions and dead code paths while preserving essential framework ceremony and security guards.

Reviewing legacy code for technical debt is best handled by generating a non-destructive advisory report categorizing findings into delete-lists and watch-lists, flagging speculative configurations and unused parameters for developer verification.

Pruning code bloat without breaking framework ceremony or security guards requires applying a YAGNI-based review that explicitly preserves essential structures, outputting a non-destructive advisory report with delete-lists and watch-lists for manual verification.

YAGNI code review does not automatically delete dead code paths; it operates non-destructively by producing an advisory report with delete-lists and watch-lists, requiring developer verification before any code deletion occurs.

You can analyze git diffs to find single-use abstractions and premature generalizations by applying a YAGNI-based complexity ladder to the changes, flagging over-engineering instances in a structured advisory report for developer review.

Avoid using a YAGNI-based complexity ladder when code heavily relies on complex framework ceremony or security guards that could be misinterpreted as bloat, though the non-destructive advisory report ensures limitations only impact manual verification workload.