simplify-code

Safely refactor over-engineered code by inlining single-use helpers and removing pass-through wrappers while proving existing behavior holds through unchanged passing tests. A green baseline test suite is required before simplifying structure and tightening guarantees.

Reduce code duplication by detecting repeated logic across files and centralizing it once it appears in three or more places. Stricter consolidation rules apply to sensitive areas like auth, billing, redirects, cookies, logging, and external APIs.

Remove single-use abstractions and dead configuration when a reviewer flags over-engineering, a wrapper has only one caller, or a cleanup is needed before implementing a harder feature change. Always apply deletion-test and Chesterton's Fence reasoning first.

Yes, a green baseline test suite is required to simplify your codebase. Tests must remain unchanged and pass before and after removing unnecessary abstractions, centralizing repeated patterns, and deleting dead flags.

If a refactoring change alters assertions, discovers bugs, or finds missing tests, the simplification process enforces a strict handoff. It stops immediately when a change would alter existing behavior or break the green-test baseline.

Chesterton's Fence reasoning requires understanding why an abstraction or dead flag exists before removing it. You must verify all call sites and run deletion-test checks to ensure structural simplification does not break existing product behavior.