grimdevgit-commit-decanterlisted

# Git Commit Decanter Decant one monster diff into clean, settled chunks. Grim workflow layer on top of [git-surgeon](https://github.com/raine/git-surgeon): non-interactive hunk-level git operations for precise staging, splitting, and history shaping. Upstream CLI: `git-surgeon` (currently tested against `0.1.17+`). ## Invocation Scope Use this skill for most git workflows that involve: - planning commits - staging or splitting hunks - cleaning up a dirty tree - amending, folding, squashing, reordering, or otherwise shaping history - preparing a reviewable commit stack Do not invoke it for simple read-only `git status`, `git log`, `git show`, or `git diff` checks unless the user is asking about commit structure, cleanup, or history work. ## Default Workflow (Plan First, Then Commit After Approval) Default behavior when the user invokes this skill: - inspect the current branch's uncommitted changes - split them into a proposed stack of small, easily reviewable commits - present a numbered commit list for user approval - only execute the plan after the user approves it Do not silently commit immediately after creating the plan unless the user explicitly pre-approves that behavior in the request. Target commit count: default to between 3 and 20 commits. - If the first pass produces fewer than 3 commits, look again for valid separations such as setup, behavior, refactor, tests, docs, tooling, or follow-up cleanup. - Do not create fake or noisy commits just to hit the f