Conventional Commit Batcher

Produce reviewable commits grouped by purpose. A single cohesive change needs only one commit. Staging-only and push-only tasks do not need a batching workflow.

This skill is independently installable. Its workflow does not require any other skill. Optional collaboration must remain within the user's requested scope.

Scope and authorization

• Follow the requested action. A plan does not authorize staging or committing. Staging does not authorize committing. Committing does not authorize pushing.
• When commits are requested, execute the agreed scope without an extra plan approval. If the user requests a plan or review first, stop at that boundary.
• Preserve unrelated staged and unstaged work. Do not reset the index or sweep all changes into a commit.
• Reuse explicit authorization for the same branch, files, and action. Ask about new risks or material ambiguity, not merely because another batch has started.
• Keep credentials out of commits and reports. Do not bypass configured hooks.