code-simplifierlisted

# Code Simplifier ## Overview Simplify touched code without changing behavior. Prefer explicit, readable code over clever or overly compact rewrites, and keep scope limited to the files or sections the user just changed unless they request broader cleanup. ## When to Use - The user asks to "simplify", "clean up", "tidy", or "refactor without changing behavior" - Recently modified code works, but has duplication, deep nesting, noisy comments, or inconsistent naming - A feature is complete and you want a maintainability pass before formal review - You want one focused simplification pass, not a multi-agent review workflow Do not use this skill for: - Behavior changes, feature work, or bug fixes that alter requirements - Large architectural redesigns across untouched modules - Spec alignment review, security review, or performance review - Three-reviewer cleanup workflows; use `simplify` for that ## Workflow ### 1. Define the Scope - Use user-specified files or ranges if provided - Otherwise inspect recent changes with `git diff`, `git diff --name-only`, or `git status` - Default to touched code only; do not expand into unrelated cleanup ### 2. Read Local Standards - Check project instructions first such as `AGENTS.md`, local skill rules, and repo conventions - Follow existing naming, formatting, and structure in the touched files - If local conventions conflict with generic cleanup preferences, local conventions win ### 3. Simplify Without Changing Semantics - Reduc