git history cleanup

purpose

Transform experimental development history into a clean, reviewable commit sequence where:

• Each commit is atomic: contains one logical change that builds/tests successfully
• Commits are logically ordered: dependencies come before dependents, related changes are grouped
• Intermediate commits are removed: no "WIP", "fix typo", "oops", or checkpoint commits
• Each commit message follows conventional commit format and accurately describes its diff

This prepares branches for PR review by creating a clear narrative of what changed and why.

GitButler mode

When gitbutler/workspace is checked out, the but CLI provides native history editing commands that replace git rebase -i. The git-rebase patterns in the rest of this skill apply only to git-native mode.