commitlisted

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`