Create bounded commits

Process skill — make related uncommitted work reviewable as separate local commits without losing unfinished work.

Entry gate

• The user asks to organize, group, or commit uncommitted work.
• Default to automatically committing obvious groups under the eligibility gate below. An explicit request to inspect, propose, or stop before committing takes precedence: present the groups and make no commits until authorized.
• Operate on the current checkout and current branch only. This skill never pushes, merges, changes branches, repairs product code, or globally installs itself.

Automatic commit eligibility

A group is obvious only when all of these are established from evidence:

• It has one clear purpose, complete content, and an unambiguous boundary. It requires no discretionary split between finished and unfinished hunks.
• Its dependencies are included or already present in captured HEAD/earlier validated groups. It borrows no deferred work.
• Local evidence establishes readiness, with targeted chat inspection only when the chat relevance gate below is met; no unresolved ownership question, critical conflict, or concurrent write threatens the group or shared branch/index state.
• Required isolated candidate checks pass, normal hooks pass without changing content, and staged/unstaged/untracked preservation can be verified.