at-commit

# Commit Message Generator ## Workflow 1. Run `git diff --staged` to inspect staged changes. If it is empty, tell the user to run `git add` first and stop. 2. Determine the description language using the Language Policy below. 3. Generate the message(s) and show them for confirmation; do not commit immediately. When more than one framing is reasonable, present them as a short numbered list (`1)`, `2)`, …) so the user can pick by replying with just the number. A single clear message may be shown on its own. The user may also reply with an edit or their own wording. 4. Run `git commit -m` only after the user picks or explicitly confirms — a number from the list, "commit", or "ok" all count. Do not run `git push` unless the user explicitly asks. ## Language Policy Use this priority order for the human-readable description after `type(scope):`: 1. Use the language explicitly requested by the user in this turn. 2. Otherwise use the repository preference in `.agent-tools/config.jsonc`, if it defines `at-commit.language`. 3. Otherwise use the global preference in `~/.agent-tools/config.jsonc`, if it defines `at-commit.language`. 4. Otherwise use the language of the user's actual invocation text when it contains a clear, independent natural-language request. Ignore injected skill instructions, quoted or pasted content, code blocks, diffs, and tool output. 5. Otherwise match the dominant language in recent repository commit subjects. 6. If no dominant language is clear, default t...