commit

# Commit workflow Work the steps in order. A guard hook runs alongside them and refuses whole-tree staging along with any `git commit` you write out yourself. Step 8 names the one script that commits, and that script refuses an inline `-m` message, a `--no-verify`, and a draft the reviewer hasn't seen in its current form. Those hooks stay registered for the rest of the session so they carry a scope. Preflight arms the guard at the commit `HEAD` sits on now. Step 8 moves `HEAD` past that mark and stands the guard down. Work later in the session is none of the guard's business. A second commit means invoking this skill again rather than carrying on from here. ## Preflight !`bash ${CLAUDE_SKILL_DIR}/scripts/preflight.sh` ## Step 0: open the task list Create these tasks with `TaskCreate`, then move each to `in_progress` and `completed` as you go. They're the checklist the rest of this document expands. 1. Choose the rebase base 2. Group the changes into atomic commits 3. Stage the paths for this commit 4. Draft the message in COMMIT_AGENTMSG 5. Clear the prose gates with fix-prose 6. Review the draft with review-commit-message 7. Run the commit-msg gates 8. Confirm the message with the operator 9. Commit and rebase Stop before any of it if preflight reports a rebase, merge, or cherry-pick in progress, or a missing precondition. Say what's wrong and hand back. ## Step 1: choose the rebase base Preflight computed this under `== rebase base ==`. Take its recommendation: -...