commit-pushlisted

> **Script path fallback**: qq scripts are invoked as bare commands (e.g. `unity-test.sh`). If "command not found", use `${CLAUDE_PLUGIN_ROOT}/bin/<command>` instead. Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md). Batch commit all uncommitted changes and push to the remote repository. ## Steps 1. If `qq-project-state.py` is available, run it first: ```bash qq-project-state.py --pretty ``` Interpret it like this: - `recommended_next == "/qq:commit-push"` → normal ship path, continue - otherwise → stop and tell the user the actual next step first - if the user explicitly says to force the push anyway, note the risk and continue 2. Run `git status -u` and `git diff --stat` to view all uncommitted changes 3. Analyze the changes and group them by **logical relationship** (do not mix unrelated changes into the same commit): - Feature code changes in one group (feat/fix/refactor) - Asset files (prefabs, assets, scenes) in one group - Config/docs in one group - If all changes belong to the same feature, a single commit is fine 4. For each group: - `git add` the relevant files (do not use `git add -A`; specify files individually) - Write a commit message in conventional commit style - Append `Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>` at the end of the commit message 5. After all commits are done, run `git push` 6. **Worktree closeout** — detect