What problem does it solve? Iterative development leaves branches full of fixup commits, WIP snapshots, and interleaved refactors that are painful to review. This Skill reshapes the commits a branch carries on top of its target branch into a clean, logical sequence where each commit tells one story, without changing the final committed tree. ## Core Features & Use Cases - Commit sequence planning: Reads the full diff from the merge base and designs an ordered sequence where each commit is independently buildable and testable. - Safe history rebuild: Folds existing fixup commits with autosquash or performs a full rebuild with hunk-level staging via git-hunk or patch-based fallback, always keeping a recorded recovery point. - Per-commit verification: Runs planned checks on every commit in an isolated temporary worktree and validates that the final tree matches the original branch tip exactly. - Use Case: Before opening a PR, a developer with a dozen messy commits uses this Skill to reorganize them into three reviewable commits (a refactor, a standalone fix, and the feature), each passing lint and type checks on its own. ## Quick Start Use the recommit skill to tidy this branch's unmerged commits into a clean logical sequence before I open the pull request.