eisland-dev-git-commit

# Git Status Analysis and Commit Analyze the current git working tree, understand what changed and why, then create a well-formatted commit with an English message. ## When to use - The user asks to commit their current changes - The user wants to analyze what's changed and create a commit - The user says "提交", "commit", "git commit", or similar - The user wants to review and save their work to git ## Process ### Step 1: Check git status Run these commands to understand the current state: ```bash git status git diff --stat git diff --cached --stat ``` This tells you: - Which files are modified, added, or deleted - Which files are staged vs unstaged - The scope of changes ### Step 2: Analyze the changes For each changed file, read the diff to understand what was actually changed: ```bash git diff <file> # for unstaged changes git diff --cached <file> # for staged changes ``` Categorize changes by type: | Type | Prefix | When to use | |------|--------|-------------| | **feat** | `feat` | New feature or user-facing functionality | | **fix** | `fix` | Bug fix | | **refactor** | `refactor` | Code restructuring without behavior change | | **style** | `style` | Formatting, whitespace, semicolons (no logic change) | | **docs** | `docs` | Documentation only | | **test** | `test` | Adding or updating tests | | **chore** | `chore` | Build config, dependencies, tooling | | **i18n** | `i18n` | Internationalization changes | | **perf** | `perf` | Performance improvement...