Simplify

Overview

Use this as a pre-review cleanup gate. The goal is not formal approval; it is to inspect changed code for reuse opportunities, code quality issues, and efficiency issues, then fix the worthwhile findings without changing behavior.

When to Use

• The user wants a /simplify-style cleanup pass before reviewer or code-reviewer
• A feature is complete and the diff likely contains duplication, rough edges, or avoidable inefficiency
• You want to reduce avoidable reviewer comments before formal review
• The change spans enough files or logic that one simplification pass is not enough

Do not use this skill for:

• Tiny diffs where a single local cleanup is enough
• Behavior changes, feature work, or bug fixes that alter requirements
• Large architectural redesigns across untouched modules
• Formal spec validation or security review