commit-zh

Original：🇨🇳 Chinese

Translated

Chinese Git Commit Skill. Analyze changes and generate Chinese conventional commit messages. Triggered when the user says "submit", "commit", "submit code", "submit changes", or "/commit-zh". Executed entirely by the main agent, no subagents used.

5installs

Sourceliao666brant/agent-tools

Added on2026-05-28

NPX Install

npx skill4agent add liao666brant/agent-tools commit-zh

SKILL.md Content (Chinese)

View Translation Comparison →

Chinese Git Commit

Analyze staged/unstaged changes and generate Chinese conventional commit messages, executed entirely by the main agent.

Conventional Commit Format

<type>[(scope)]: <Chinese description>

[Optional body]

[Optional footer]

type/scope must always be in English, subject/body/footer in Chinese.

Commit Types

Type	Purpose
`feat`	New feature
`fix`	Bug fix
`docs`	Documentation changes
`style`	Formatting/style changes
`refactor`	Code refactoring
`perf`	Performance optimization
`test`	Testing-related changes
`build`	Build system/dependencies
`ci`	CI/configuration changes
`chore`	Maintenance/miscellaneous
`revert`	Revert a previous commit

Workflow

1. Check Repository Status

bash

git status --porcelain

Stop if there are no changes.

2. Analyze Diff

bash

# Use staged diff if there are staged files
git diff --staged

# Use workspace diff if no files are staged
git diff

3. Stage Files (If Needed)

Stage files in logical groups when no files are staged:

bash

git add path/to/file1 path/to/file2

Group by logical relevance
Prohibit staging files that may contain secrets (.env, credentials, private keys)
Prohibit
```
git add .
```
/
```
git add -A
```
Multiple logical units → Suggest splitting into multiple commits

4. Generate Commit Message

Type: Change type (English)
Scope: Directory/module name (English, optional)
Subject: Chinese summary, imperative mood, ≤72 characters
Body: List with
```
- 
```
explaining why/what, ≤3 items, each ≤72 characters
Footer: Breaking changes/issue references

Format Constraints

Subject ≤72 characters, no period
Body: Blank line after subject, starts with
```
- 
```
, explains intent and reason
Footer: Blank line after body, git trailer (e.g.
```
Closes #123
```
), use
```
BREAKING CHANGE: <description>
```
and add
```
!
```
after type for breaking changes

Examples

text

feat(auth): 添加 OAuth2 登录支持

- 实现 Google 和 GitHub 第三方登录
- 添加用户授权回调处理
- 优化登录状态持久化逻辑

Closes #42

text

feat(api)!: 重新设计认证 API

- 从 session 认证迁移到 JWT
- 更新所有端点签名
- 移除已废弃的登录方式

BREAKING CHANGE: 认证 API 已完全重新设计，所有客户端需更新集成

5. Execute or Suggest Splitting

Single logical unit: Commit directly without confirmation
Multiple logical units: Suggest splitting, execute after confirmation

6. Execute Commit

bash

git commit -m "$(cat <<'EOF'
<type>[(scope)]: <中文描述>

<body>

<footer>
EOF
)"

Prohibit automatic push. Only commit locally unless explicitly requested by the user.

7. After Commit

bash

git log --oneline -1

Security Protocol

Prohibit modifying git config
Prohibit destructive commands (--force, hard reset) unless explicitly requested by the user
Prohibit skipping hooks (--no-verify) unless explicitly requested by the user
Prohibit committing files containing secrets or potentially containing secrets
Commit single logical changes directly; suggest splitting multiple logical units and wait for confirmation
Prohibit automatic push, only commit locally

commit-zh

NPX Install

Tags

SKILL.md Content (Chinese)

Chinese Git Commit

Conventional Commit Format

Commit Types

Workflow

1. Check Repository Status

2. Analyze Diff

3. Stage Files (If Needed)

4. Generate Commit Message

Format Constraints

Examples

5. Execute or Suggest Splitting

6. Execute Commit

7. After Commit

Security Protocol