simplify

Code diff simplification identifies smaller, behavior-preserving changes by locating confirmed opportunities to remove unnecessary complexity like dead code, redundant logic, and speculative abstractions. It requires diff-scope inspection to produce evidence-based verdicts with proof and verification steps.

To reduce risky churn in refactoring changes, locate confirmed opportunities to remove unnecessary complexity across single or multiple file clusters. Produce evidence-gated recommendations that clearly answer what to change, why it is lower risk, and what verification to run before deeper review.

Yes, you can automatically apply behavior-preserving simplifications to a local diff by running the process with the --auto flag. This applies only confirmed, safe changes that remove unnecessary complexity without altering the original software behavior.

Diff simplification works on large multi-file code changes by dispatching a focused simplifier approach for larger or multi-area changes. It uses scope-aware rules to inspect the actual changed code rather than just summaries, choosing direct inspection for smaller diffs for efficiency.

The best way to verify a code simplification is behavior-preserving is to use evidence-gated recommendations that require clear proof for each finding. Each verdict must answer what local pattern proves it and what specific verification steps to run before applying the change.