git-commit

Use this workflow in order: preflight -> split plan -> classify -> compose -> commit/draft -> verify.

Decide the active change authority and output language before doing anything else:

• staged-only is the default. Respect the current index and treat unstaged or untracked files as context only.
• all-changes is allowed only when the user explicitly asks to include everything, such as "all changes", "所有改动", "全部改动", "不管有没有 stage", or "包括未跟踪文件". In this mode, the skill may rebuild the index from the full working tree and should treat any existing partial staging as intentionally overridden by the user.
• english-output is the default. Use English for commit scope, subject, body, and explanatory output.
• chinese-output is allowed only when the user explicitly says 请使用中文拆分提交所有的改动. Treat other Chinese-language prompts as english-output unless they include that exact phrase.

1. Preflight

1. Inspect git status --short first. Then inspect the active change set:
   • staged-only: git diff --staged --stat and git diff --staged
   • all-changes: git diff --stat, git diff, git diff --staged --stat, and git diff --staged If rtk is available, prefer rtk git status, rtk git diff --staged, and rtk git diff for model-visible inspection.
2. Explicitly note:
   • the active change authority (staged-only or all-changes)
   • staged changes ready to commit
   • unstaged changes that might make the index misleading