code_simplifier

Code smell detection scans changed code for parameter sprawl, copy-paste duplication, and leaky abstractions. It inspects your post-change diff to identify duplicated logic and awkward abstractions, delivering concrete cleanup changes before merging.

The best way to reduce tech debt is performing a post-change code review to eliminate low-quality, duplicated, or inefficient code. This targets recent modifications to remove awkward abstractions and bloat without rewriting unrelated stylistic code.

Efficiency review checks modified code for repeated work, unnecessary reads, event churn, and hot-path bloat that cause performance regressions. It inspects your latest diff to pinpoint and fix these specific inefficiencies.

Yes, code simplification eliminates low-quality and duplicated logic from changed code while avoiding unnecessary stylistic rewrites. It strictly targets the post-change diff to remove bloat and reuse existing utilities without touching unrelated code.

You need diff inspection for code simplification immediately after implementing new features or development changes. It catches accidentally introduced duplicate logic, awkward abstractions, and performance inefficiencies before they create long-term tech debt.