Review and simplify changes

Overview

Use this skill after a commit, PR, branch, or WIP diff to improve code quality without speculative churn.

When to Use

• Reviewing or simplifying changes after a commit, PR, branch, or work-in-progress diff
• Checking changed code against repo Standards and change Intent from the prompt, explicit spec, plan, task notes, issue, or commit message
• Finding duplication, weak types, dead code, cycles, fallbacks, comments, or code quality issues introduced or exposed by the change
• Applying high-confidence, behavior-preserving cleanup when the user asks for fixes, then validating it

When Not to Use

• Use debugging first when behavior is broken and cause is unknown
• Use improve-codebase-architecture for architecture plans without implementation
• Use test-design when the main question is test strategy