Simplify

Simplify recently modified code for clarity, consistency, and maintainability while preserving exact behavior.

NOT for bug hunting (honest-review), debt inventory (tech-debt-analyzer), or performance-only investigation (performance-profiler).

Canonical Vocabulary

Use these terms exactly throughout all modes:

Term	Meaning
recent scope	The code changed in the current task, current diff, or explicit user target; default operating scope
simplification pass	A behavior-preserving cleanup focused on clarity, structure, or redundant machinery
behavior preservation	Keeping the same externally observable behavior, contracts, outputs, side effects, and error boundaries
semantic change	Any change that alters behavior, API shape, validation rules, ordering guarantees, error semantics, or security posture
mechanical cleanup	Low-risk edits like removing obvious redundancy, flattening nesting, renaming for clarity, or deleting dead comments
redirection	Explicitly refusing out-of-scope work and naming the correct skill to use instead