tidy-history

Rewrite a topic branch's unmerged commits so each has one logical purpose, a sensible rollback boundary, and a valid message, without changing the branch's final tree, then publish the result with a lease. Use when the user asks to tidy or clean up branch history; to squash, fold, reorder, split, reword, or amend existing commits, including amending working-tree changes into one; to fold review fixes into the commits they correct; or when another git skill directs applying git:tidy-history. Do not use for committing changes as new commits, rebasing a branch onto an updated target, resolving conflicts, squash-merging a pull request, inspecting history, or conceptual questions about rebasing.

License

MIT