code-simplifier

Run a simplification pass scoped to your current diff or changed files. The process preserves exact behavior, return values, and public contracts while improving naming, flattening nesting, and removing redundant condition checks.

Apply the smallest set of edits that improve clarity: replace nested ternaries with if/else chains, use guard clauses to reduce nesting, rename unclear variables, and remove comments that only restate obvious code. Re-check types and tests afterward.

Yes. Before simplifying, the workflow reads active repository instruction files such as AGENTS.md, CLAUDE.md, or generated workspace instructions, then aligns the cleanup with those standards and existing error-handling patterns.

Avoid it when you need behavioral changes, broad cross-file refactors, or architectural redesign. The scope is deliberately limited to recently modified code, and it will not merge unrelated concerns or remove meaningful abstractions.

Nested ternaries compress multiple branching decisions into one expression, making logic hard to scan and debug. Explicit if/else chains or switch statements communicate multi-directional conditions more clearly to future maintainers.