simplify-for-readability

To simplify code for readability, remove indirection, inline short helpers, avoid single-use constants, and preserve native defaults. This refactoring approach maximizes scanability while ensuring the observable behavior of the code remains completely unaltered.

Indirection removal eliminates unnecessary abstraction layers, while inlining helpers collapses small, single-use functions back into the calling code. Apply both during refactoring to reduce complexity and duplicate state, mapping shared state only at the boundary.

Yes, you can enforce minimal control flow during code reviews by preferring single expressions where possible. This ensures readability remains the primary metric, advising when to collapse duplicate state and inline short helpers without altering behavior.

Yes, this readability refactoring approach applies across languages and projects. It provides practical examples for code generation, modification, and review projects, ensuring readability is prioritized through indirection removal and preserving default behavior regardless of the language.

Avoid inlining helpers or removing indirection if doing so alters the observable behavior of the code. Run this simplification check before finalizing any code change to verify that reducing complexity and collapsing state preserves the original default behavior.