commit

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Git Commit

Context

背景信息

Current git status: !
```
git status
```
Current git diff (staged and unstaged changes): !
```
git diff HEAD
```
Current branch: !
```
git branch --show-current
```
Recent commits: !
```
git log --oneline -10
```

当前Git状态：!
```
git status
```
当前Git差异（已暂存和未暂存的更改）：!
```
git diff HEAD
```
当前分支：!
```
git branch --show-current
```
最近的提交：!
```
git log --oneline -10
```

Commit Rules

提交规则

Size

提交粒度

Small logical steps forward. Each commit = one feature, one fix, or one refactor.

小步逻辑推进。每个提交对应一个功能、一个修复或一次重构。

Message Format

提交信息格式

<concise title in Korean>

- WHY point 1
- WHY point 2

Title: Concise Korean summary (50 chars max)
Body: 1-3 bullet points explaining WHY we made this change (not WHAT changed)

<简洁的韩语标题>

- 原因要点1
- 原因要点2

标题：简洁的韩语摘要（最多50字符）
正文：1-3个项目符号，说明我们为什么做这个更改（而非更改了什么）

No AI Signatures

禁止AI签名

Never include:

```
Generated with [Claude Code]
```
```
Co-Authored-By: Claude
```
Any emoji or AI branding

绝不要包含：

```
Generated with [Claude Code]
```
```
Co-Authored-By: Claude
```
任何表情符号或AI品牌标识

Good vs Bad Examples

正反示例

undefined

undefined

BAD - describes WHAT changed (obvious from diff)

反面示例 - 描述了更改内容（从差异中可明显看出）

토큰 사용량 추적 버그 수정

Changed modelUsage.tokens to usage.input_tokens
Added try-catch block

토큰 사용량 추적 버그 수정

将modelUsage.tokens修改为usage.input_tokens
添加try-catch块

GOOD - explains WHY we made changes

正面示例 - 说明了更改的原因

토큰 사용량 추적 버그 수정

API response structure changed in v2, tokens now nested under modelUsage
Fallback needed for backward compatibility with older API responses

undefined

토큰 사용량 추적 버그 수정

API v2版本中响应结构变更，令牌现在嵌套在modelUsage下
为了与旧版API响应向后兼容，需要添加回退机制

undefined

Your Task

你的任务

Based on the above changes and rules, create a single git commit. Stage and commit using a single message. Do not use any other tools or send any text besides the tool calls.

基于上述更改和规则，创建一个Git提交。使用一条提交信息完成暂存和提交。除工具调用外，不要使用任何其他工具或发送任何文本。