commit-batching

Partition a mixed-delta working tree into ordered conventional commits.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/aleister1102/skills --skill commit-batching
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-batching
Source: https://github.com/aleister1102/skills/tree/main/commit-batching
Command: npx skills add https://github.com/aleister1102/skills --skill commit-batching

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break a mixed-delta working tree into focused conventional commits by planning the sequence, staging deliberate hunks, and reviewing each set before committing.

Core Features & Use Cases

  • Plan and stage commits to reflect distinct features, fixes, or refactors.
  • Define an ordered sequence of commits to support code reviews and release notes.
  • Adapt to multiple changes across a single working tree, ensuring each commit remains focused and testable.

Quick Start

Draft a commit plan that groups changes by feature, stage each group interactively with git add -p, and commit them with conventional messages.

Frequently Asked Questions about commit-batching

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I split a mixed working tree into multiple conventional commits?

To split a mixed working tree into conventional commits, you plan a commit sequence grouping changes by feature, stage each group interactively with git add -p, and commit them with clear messages.

What is the best way to organize git commits for code review and release notes?

Organizing git commits for code review involves partitioning a mixed-delta working tree into discrete, focused commits, ensuring each commit remains distinct, readable, and testable for reviewers.

Can I batch feature, bug fix, and refactor changes into an ordered git history?

You can batch feature, bug fix, and refactor changes by applying a multi-commit workflow that partitions changes across a single working tree into an ordered, readable git history.

Do I need external tools to partition a mixed-delta working tree into clean commits?

Partitioning a mixed-delta working tree requires no external tools beyond standard git commands and basic best practices to validate, stage, and commit changes with clear messages.

How does interactive staging help create focused conventional commits?

Interactive staging helps create focused conventional commits by allowing you to deliberately stage specific hunks of a mixed working tree, ensuring each commit reflects a distinct feature or fix.