commit-chunkslisted

# Commit in Logical Chunks Post-hoc split of a dirty tree into logical commits. Use `/commit-all` if there is only one topic. Review all staged and unstaged changes in the current repo, then group them into logical commits and execute them one at a time. ## Steps 1. Run `git status` and `git diff` to see all changes 2. Group changed files by topic/feature/fix into logical chunks (e.g. "feat: X", "fix: Y", "data: Z") 3. For each chunk in order: - Stage only the files for that chunk - Write a concise commit message (imperative, present tense, no em dashes) - Commit with Co-Authored-By trailer 4. After all commits, confirm what was committed ## Chunking rules - Never batch unrelated changes in one commit - One feature = one commit, one fix = one commit, one data update = one commit - Generated/output files (reports, logs, cache) are separate from the script that generated them - Merge solo-file chunks into a topically similar adjacent chunk where possible - a lone unrelated file is usually an artificial split - Always include session logs (bash-audit, skill-usage, etc.) as a final `log: session update` chunk - never skip them - Co-Authored-By line: use the active Claude model, e.g. `Co-Authored-By: Claude <model> <noreply@anthropic.com>` on every commit. - After committing log files, STOP - do not re-check git status (hook-generated log files create an infinite loop if you keep checking) ## File moves - split into two commits When files are moved to a new locati