Writing code is messy. Git history doesn't have to be.
During development we experiment, refactor, backtrack, and fix mistakes. If every step ends up as a commit, the history becomes noise. A curated history turns that process into a clear sequence of logical changes.
git-stage-batch helps you build that history incrementally by letting you stage changes hunk-by-hunk or line-by-line, shaping commits around meaning instead of the order the edits happened.
halfline•41m ago
It's a tool for turning a chaotic working tree into clean Git history before pushing.
git-stage-batch adds named deferred change sets (“batches”), multi-pass staging, and finer-grained (line level) patch selection on top of the usual hunk workflow. I built it because `git add -p` and `git rebase` alone weren’t enough for large refactors. Its CLI mode is especially useful for getting AIs to help organize commits from a dirty working tree.
Interested in feedback from people who obsess over commit hygiene.