Sensible Commit Flow

Commit history should reflect the work, with each commit making sense on its own.

This skill helps agents group changes by intent, order commits by dependency, and write messages that explain their purpose. It presents the plan for your approval before creating commits or revising unpushed history, then verifies the recorded result while preserving unrelated work.

Workflow

For prospective commit planning before changes exist, follow Plan Before Implementation and return to the calling workflow without entering confirmation or execution.

Select Update Unpushed Commits only when the user or an applicable calling workflow explicitly requests a history update or rebase. A request to fold changes into their original commits selects that route without requiring Git terminology.

For new commits assembled from working tree changes, prepare the proposal through Inspect Changes, Group Hunks, and Compose Messages. For cherry-picks and merges that create commits, including continuation after a pause, prepare it through Preserve Operation Messages instead. Every execution route then follows Confirm Commits, Create Approved Commits, and Report the Result, in that order.

Before invoking a script or test that creates commits, inspect its implementation and inputs to establish the target repositories and expected commit sequence. Select the applicable route for those commits rather than assuming the invoking repository’s diff represents them. Include the exact invocation in confirmation, and obtain approval to create the proposed batch through that command. Invoke it only if it can satisfy the selected route’s inspection, preservation, validation, and verification requirements at that route’s defined checkpoints. Otherwise, report what cannot be established or satisfied and stop before invocation.

For newly authored messages, proposal explanations, and result prose, apply Writing Composition within the selected route.

Authorization