commit-with-promptslisted

# Commit with prompts Commit the working-tree changes produced during this conversation, using a commit message that documents the prompts that produced them. ## Steps 1. **Check the repo.** Run `git status`, `git diff`, `git diff --staged`, and `git log --oneline -5` (in parallel) to see what changed and to match the repo's existing commit style. If the directory is not a git repository, stop and ask the user whether to run `git init`. 2. **Confirm scope.** Stage the files this conversation actually touched. Do not stage unrelated pre-existing changes, build output, or anything matching `.gitignore`-worthy patterns. If there is nothing to commit, say so and stop. 3. **Collect the prompts.** Walk the conversation from the first user message to the latest, in order. Include every user-authored prompt, including the one that invoked this skill. Exclude: - system reminders, hook output, and tool results - command/skill scaffolding the user did not type If this conversation already produced a commit from this skill, start from the first prompt after that commit instead. Do not repeat prompts an earlier commit already logged, since duplicating them across commits obscures which prompts produced which diff. Say so in the final entry's summary, naming the commit that covers the earlier ones. 4. **Write the message body** in the format below. 5. **Commit.** Write the message to a temp file (`mktemp`, or the session's scratchpad dir