Code Simplification Assistant

Problem

Code that works but is hard to maintain is the core issue this skill addresses. It does not optimize for fewer lines; it makes already-working code easier to read, modify, debug, and review. Typical cases include implementations that feel heavier than the problem, review feedback about deep nesting or vague names, duplicated logic scattered across files, and inconsistencies introduced after merges.

How It Works

The skill treats simplification as a controlled process:
- Understand first: Before removing or rewriting code, determine why it exists, so you do not delete a Chesterton’s Fence.
- Spot concrete signals: for example, 3+ levels of nesting, functions over 50 lines, boolean flags like doThing(true, false, true), names such as data or temp, duplicated blocks, and valueless wrappers.
- Apply incrementally: make one simplification at a time, run tests after each change, and keep refactoring separate from feature work.
- Verify the result: revert if the “simplified” version is harder to review, requires test changes, weakens error handling, or creates noisy diffs.

Scope and Limits

It is best used on stable, test-covered code. It is not intended for performance-critical paths, behavior you still do not understand, modules about to be rewritten, or code that is already clean. The goal is lower comprehension cost, not blind line-count reduction.