simplify

To shrink a git diff safely, the skill removes redundant or speculative logic from your change set while preserving correctness. It generates deletion candidates with risk assessment and applies only approved surgical edits, verifying results via the project's fast checks.

Diff simplification is a post-review shrink pass that reduces overly complex or redundant changes in a code diff. You should use it only after your diff is cleanly reviewed to make reviews faster and diffs easier to reason about.

You can remove redundant code from staged changes by supplying the staged diff to the simplification process. It identifies concrete removal opportunities like premature abstractions and dead branches, then asks you to accept or decline each deletion candidate.

Yes, you can simplify specific file paths, the last commit, explicit ranges, or the current working tree. The process applies diff-only simplification to shrink only the provided change set without restructuring unrelated code.

During safe refactoring, the process identifies premature abstractions, dead branches, redundant comments, and impossible-path error handling as deletion candidates. Each candidate is risk-assessed before you decide to accept or decline the removal.

You should not use diff simplification before your diff is cleanly reviewed. The process enforces a review-order safety guardrail and will warn you if invoked early, as it is intended strictly as a post-review shrink pass.