commit

Close the loop: harvest the session's learnings first, then create well-crafted git commits from the working tree — learning writes included, so the tree is clean when the loop ends.

Step 1: Scan for compound candidates

Scan the whole session for candidate learnings: root causes uncovered, gotchas hit, approaches that failed, conventions or preferences decided along the way — plus anything /review-gate flagged as compound material.

Judge each against compound's quality bar — would it change a future agent's behavior in a different session, and is it non-obvious and stable? Session-specific trivia dies here.

• Any candidate might clear the bar → invoke /compound with the candidates; it routes each to a destination and gates every write on the user. Once the approved writes land, present their diff and wait for the user's verdict on the wording — approve, edit, or drop each document — since the destination gate cleared a one-line proposal, not the prose itself. Writes that survive ride into the commits below.
• None → say so in one line and move on.

Step 2: Gather context

Gather context with each command as its own shell tool call (program + args only). Do not join with ;, &&, ||, pipes, $(...), or redirects — that syntax fails under Windows PowerShell. A non-zero exit is a normal state to interpret, not a failure to suppress.

• git status — working-tree state. Clean tree → report there is nothing to commit and stop.
• git diff HEAD — the uncommitted changes.
• git branch --show-current — empty output means detached HEAD.
• git log --oneline -10 — recent commit style.
• git rev-parse --abbrev-ref origin/HEAD — the default branch (strip the origin/ prefix). If unset, fall back to main.

Treat this as a snapshot. Re-read branch and staged set immediately before committing if anything may have changed.

Step 3: Choose the branch

Detached HEAD → cut a feature branch before committing, and do not ask — even where the user asked only for a commit, since a commit reachable from nothing is lost as soon as HEAD moves. On the default branch, follow the repo's workflow instead: where the documented conventions or recent history show feature branches (or the user asked for one), branch off it before committing. Where the history shows commits landing directly on it (trunk-based), commit where you are. On any other branch, commit where you are unless the user asked for a new one.