cleanup-commits

To reorganize messy Git commits for PR review, this Skill groups related changes into cohesive commits and executes a scripted rebase workflow to squash or reorder commits without losing changes. It uses a plan-and-verify loop to ensure history remains readable and branches stay attached to the base branch.

The best way to squash commits on a local feature branch is using a plan-and-apply workflow that safely previews and executes an interactive rebase. This Skill groups related changes into logical commits and applies guardrails to prevent data loss while preserving readable history.

Yes, you can use an interactive rebase workflow without losing changes because this Skill enforces guardrails through a plan-and-verify loop. It safely plans, previews, and executes squashing or reordering to ensure branches remain attached to the base branch and history is preserved.

To group related code changes into cohesive commits for version control, this Skill reorganizes messy commits based on logical features, fixes, or refactors. It supports a base-branch parameter and uses a scripted rebase to deliberately group commits into a clean, PR-ready sequence.

Yes, this commit cleanup workflow supports specifying a custom base branch parameter to ensure your reorganized commits remain properly attached. The plan-and-apply workflow uses this parameter to enforce guardrails and maintain readable history during the rebase process.

You should avoid rebasing commits manually when you need to preserve history without guardrails against data loss. This Skill provides a safer alternative by using a plan-and-verify loop to prevent detached branches, but standard rebasing limitations regarding already-pushed shared branches still apply.