Skip to main content

git-stage-batch banner

git-stage-batch

PyPI version Python 3.10+ CI License: MIT

Fine-grained Git staging and deterministic draft-history refinement

Writing code is messy. Git history doesn't have to be.

git-stage-batch demo

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 combines fine-grained staging of uncommitted changes with deterministic refinement of clean, linear draft commits. Use hunks, lines, and batches to shape new commits around meaning, or use a validated semantic plan to reword or split commits, integrate later repairs, and reorder proven-independent changes in an existing local draft series while preserving its final Git tree. Rewriting is limited to unpublished history by default; a verified force-push review-head exception permits only the local rewrite and neither performs nor authorizes a push.

Features

  • Command-based workflow - Perfect for automation and AI coding assistants
  • Line-level control - Stage specific lines within a hunk for maximum granularity
  • Interactive mode - Menu-driven hunk-by-hunk workflow inspired by git add -p
  • State persistence - Resume staging across multiple invocations
  • Batch operations - Save hunks for later, organize complex changes
  • Deterministic history refinement - Validate and execute semantic rewrites of local draft commits
  • Machine-readable output - --porcelain flag for scripting
  • No runtime Python packages - Uses the standard library and the external Git executable

Quick Start

# Start reviewing hunks
git-stage-batch start

# Include the selected hunk (stage it)
git-stage-batch include

# Skip it for now
git-stage-batch skip

# Discard it (remove from working tree)
git-stage-batch discard

# Stage specific lines within a hunk
git-stage-batch include --line 1,3,5-7
git-stage-batch skip --line 2,4
git-stage-batch discard --line 8-10

# Check what's been processed
git-stage-batch status

# Start fresh after committing
git-stage-batch again

AI Assistant Quick Start

# Install the command
python -m pipx install git-stage-batch

# Install Claude Code commit skills into this repository
git-stage-batch install-assets claude-skills --filter 'commit-*'

# Keep the local Claude assets out of reviews
git-stage-batch block-file --local-only .claude/

# Ask Claude Code to split and commit the unstaged work
claude "/commit-unstaged-changes"

Omit --filter when installing Claude skills if you also want the larger /decompose-and-commit-unstaged-changes workflow and the standalone /refine-history BASE_SHA, /refine-commit-messages BASE_SHA, and /publish-unpushed-commits workflows. Publication creates ready-for-review GitHub pull requests or GitLab merge requests by default, supports explicit draft and audit modes, handles forks and provider-native stacks, and never merges. Selecting publication or decomposition installs both refinement dependencies. Mutating refinement accepts only a clean, linear, unpublished range or an explicitly verified force-push review head. That exception permits only a local rewrite and neither performs nor authorizes a push. Refinement resumes through the product rewrite checkpoint and its exact next action.

Example Workflow

# You have changes in multiple files
git status
# modified:   auth.py
# modified:   config.py

# Start staging
git-stage-batch start
# auth.py :: @@ -10,5 +10,5 @@
# [#1] - old_hash_function()
# [#2] + new_hash_function()

# Include this for first commit
git-stage-batch i

# Create first commit
git commit -m "auth: Upgrade to new hash function"

# Continue with remaining changes
git-stage-batch a

Why git-stage-batch?

For uncommitted changes, it is similar to git add -p but more granular and flexible:

  • ✅ Line-by-line staging - Stage specific lines within a hunk
  • ✅ Interactive mode - Continuous hunk-by-hunk workflow with menus
  • ✅ Batch operations - Save hunks for later processing
  • ✅ Colored output - Clear visual distinction in your terminal
  • ✅ File operations - Stage/skip entire files at once
  • ✅ Deterministic history refinement - Validate and execute semantic rewrites of clean draft commits

Interactive Mode

For a continuous hunk-by-hunk workflow:

# Launch interactive mode
git-stage-batch -i

# Navigate with single-key commands
# [i]nclude, [s]kip, [d]iscard, [l]ines, [f]ile, [a]gain, [q]uit

Machine-Readable Output

For scripting and automation, use the --porcelain flag:

# Get status as JSON
git-stage-batch status --porcelain

# Add active session status next to a __git_ps1 branch
PS1=$PS1'\r$(__git_ps1 "\n╎\e[32m%s$(git-stage-batch status --for-prompt=\|{status}\ {processed}/{total})\e[0m")\n'

# Check if a hunk exists (exit code 0/1)
git-stage-batch show --porcelain

Batch Operations

Save hunks for later processing with named batches:

# Create a new batch
git-stage-batch new feature-work --note "Refactoring work"

# List all batches
git-stage-batch list

# Annotate a batch
git-stage-batch annotate feature-work "Updated description"

# Drop a batch when done
git-stage-batch drop feature-work

Installation

# Using uv (recommended)
uv tool install git-stage-batch

# Using pipx
pipx install git-stage-batch

# Using pip
pip install git-stage-batch

Requirements

  • Python 3.10 or newer; CI covers current releases through Python 3.14
  • Git 2.39 or newer
  • A POSIX operating system; Linux and macOS are tested in CI. Native Windows is not supported.

Documentation

Contributing

Contributions are welcome! Please see CONTRIBUTING.md for:

  • Development setup instructions
  • A codebase guide with command paths and change checklists
  • A separate batch internals guide for saved-change storage and merge behavior
  • Commit message guidelines
  • Code style conventions

License

MIT License

Metadata

Release files for git-stage-batch 0.25.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for git-stage-batch 0.25.0
File Size Uploaded Provenance Actions
git_stage_batch-0.25.0.tar.gz 8.2 MB With provenance Details for git_stage_batch-0.25.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for git-stage-batch 0.25.0
File Interpreter ABI Platform Actions
git_stage_batch-0.25.0-py3-none-any.whl Python 3 none any Details for git_stage_batch-0.25.0-py3-none-any.whl

Total release size: 10.6 MB

Release files / git_stage_batch-0.25.0.tar.gz

Download URL git_stage_batch-0.25.0.tar.gz
Size 8.2 MB
Tags Source
SHA-256 checksum
How to use checksums
b6edc96c499b97b6a221abde29de6d3395914ce5d0fde699fc3dace0ca017d83
BLAKE2b-256 checksum
How to use checksums
4243a7cb049d4d94895eaf4b45581d0f82b9fec15f894a870aa37ca4548197a1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 21, 2026.

Transparency log

Release files / git_stage_batch-0.25.0-py3-none-any.whl

Download URL git_stage_batch-0.25.0-py3-none-any.whl
Size 2.4 MB
Tags Python 3
SHA-256 checksum
How to use checksums
0a6d0723d520aef00e97dfa1936d3a165faa8de7ffa8b02483f11123adfa78d8
BLAKE2b-256 checksum
How to use checksums
85cef7482e63677f9bbf0e240a330a492270b1b8d707314a71956f47efa5e6df
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 21, 2026.

Transparency log

Security for git-stage-batch 0.25.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for git_stage_batch-0.25.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 21, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page