chat-commit-message

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Chat Commit Message

聊天对话式提交信息

Workflow

工作流程

Read only the current conversation context in the chat window.
Do not inspect git history, staged changes, repository files, or command output.
Infer commit
```
type
```
from intent described in chat (
```
feat
```
,
```
fix
```
,
```
refactor
```
,
```
docs
```
,
```
test
```
,
```
chore
```
, etc.).
Infer commit
```
scope
```
from module names mentioned in chat. If no module scope is clearly present, use
```
global
```
.
Produce a Conventional Commit subject line in this format:
```
<type>(<scope>): <short summary>
```
Add a detailed body explaining what was requested and what was done, based only on chat context.
Add optional footer lines only when relevant (
```
BREAKING CHANGE: ...
```
, issue references, co-authors).

仅读取聊天窗口中的当前对话上下文。
不得查看git历史记录、暂存的变更、仓库文件或命令输出。
根据对话中描述的意图推断提交
```
type
```
类型（如
```
feat
```
、
```
fix
```
、
```
refactor
```
、
```
docs
```
、
```
test
```
、
```
chore
```
等）。
根据对话中提到的模块名称推断提交
```
scope
```
范围。若未明确提及模块范围，则使用
```
global
```
。
按照以下格式生成Conventional Commit主题行：
```
<type>(<scope>): <简短摘要>
```
仅基于对话上下文添加详细的正文，说明需求内容和已完成的工作。
仅在相关时添加可选的页脚内容（如
```
BREAKING CHANGE: ...
```
、问题引用、协作者信息）。

Output Rules

输出规则

Return plain text only.
Do not use markdown formatting symbols.
Keep the message easy to copy and paste into
```
git commit
```
.
Use English for all user-facing text.

仅返回纯文本。
不得使用Markdown格式符号。
确保提交信息便于复制粘贴到
```
git commit
```
中。
所有面向用户的文本均使用英文。

Quality Checklist

质量检查清单

Subject uses Conventional Commit format.
Scope is module-specific when available; otherwise
```
global
```
.
Body details are factual and grounded in chat context.
No claims based on repository inspection.
No markdown syntax in final output.

主题符合Conventional Commit格式。
范围在有模块信息时为特定模块；否则使用
```
global
```
。
正文内容基于对话上下文，真实准确。
不得包含基于仓库检查得出的内容。
最终输出不得包含Markdown语法。

Example

示例

feat(crm): add lead activity timeline filters

Implement timeline filtering controls for lead activity views as discussed in the conversation. Define filter behavior for date range and activity type and align naming with existing CRM module terminology. Document the expected behavior in the commit body using only conversation-provided context.

feat(crm): add lead activity timeline filters