Git-stage-batch – curate clean commit history before pushing

Name: Git-stage-batch – curate clean commit history before pushing
Availability: InStock
Author: twelvenmonkeys

by twelvenmonkeys·Apr 17, 2026·6 points·2 comments

Visit Project View on HN

AI Analysis

●●SolidNiche GemCozy

Git add -p but with line-level control inside hunks and batch operations across files.

Strengths

•Line-level staging within hunks is more granular than git add -p's all-or-nothing approach.
•State persistence lets you resume staging sessions across multiple terminal invocations.
•Pure Python with zero dependencies means it works anywhere without installation friction.

Weaknesses

•Audience is narrow — only developers who already care deeply about commit hygiene.
•GUI git clients (Fork, GitKraken) already offer visual hunk staging for most users.

Post Description

Hunk-by-hunk and line-by-line staging for git, designed for building clean commit history!

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.