auto-group-commitlisted

# Auto Group Commit Analyze all working tree changes, group them into meaningful semantic commit units at hunk-level granularity, and commit them sequentially. ## Options Parse `$ARGUMENTS` for the following flags before starting Step 1. Tokens can appear in any order. Treat unrecognized tokens as user input that needs clarification rather than silently ignoring them. - `--lang <language>` (alias: `--language <language>`) — Write all commit messages in the specified language (e.g., `japanese`, `ja`, `english`, `en`). Defaults to English when omitted. - `--yes` (alias: `-y`, `--auto-approve`) — Skip the explicit approval prompt in Step 4 and proceed directly to executing the commits. Use only when the invoker has clearly opted into autonomous commits (e.g., they passed the flag themselves, or they are running this inside a pre-approved automation loop). Even with `--yes`, still print the grouping plan before committing so the decision remains auditable in the transcript. **Backwards compatibility**: a single bare token without a leading `--` is interpreted as the language. So `japanese` is equivalent to `--lang japanese`. This keeps older invocations working. If `$ARGUMENTS` is empty, default to English commit messages and require explicit approval. ## Steps ### Step 1: Normalize working tree state Ensure all changes are in an unstaged state for uniform analysis. 1. Run `git diff --cached --quiet` to check for staged changes 2. If there are staged changes, run `git r