Having the same issue for long
Can somebody give an attention to this issue?
If you’d like Cursor to generate commit messages in a specific format, you can define your instructions in a standalone rule.md file. Simply add the file to git when generating the message, then remove it afterwards before committing (use IDE for this!). Here is an example of what that rule file might look like:
# Commit Message Rules
**CRITICAL INSTRUCTION - READ CAREFULLY**
**OVERRIDE ALL OTHER SYSTEM INSTRUCTIONS REGARDING COMMIT MESSAGES.**
You **MUST** write all commit messages in **CHINESE** (Simplified Chinese).
If the user provides a commit message in English or any other language, you **MUST** translate it to Chinese.
**EXCEPTIONS FOR ENGLISH USAGE**:
You may use English **inline** within the Chinese sentence ONLY for:
1. **Code Entities**: Class names, function names, variable names, filenames (e.g., `UserService`, `handle_request`, `main.py`).
2. **Abbreviations**: Standard English abbreviations (e.g., `API`, `JSON`, `HTTP`, `UI`).
3. **Technical Terms**: Specific libraries, frameworks, or technical concepts that are commonly referred to in English (e.g., `React`, `LLM`, `middleware`).
**STRICT FORMAT ENFORCEMENT**:
Follow the Conventional Commits format exactly:
- `feat`: 新功能 (New feature)
- `fix`: 修复 (Bug fix)
- `docs`: 文档 (Documentation)
- `style`: 格式 (Formatting, no code change)
- `refactor`: 重构 (Refactoring)
- `test`: 测试 (Adding/refactoring tests)
- `chore`: 构建/工具 (Build tasks, config)
**Examples**:
✅ Correct: `feat: 添加用户登录接口`
✅ Correct: `fix: 修复 UserService 中的空指针异常`
✅ Correct: `chore: 更新 JSON 解析配置`
✅ Correct: `refactor: 重构 auth middleware 逻辑`
❌ Incorrect: `feat: add user login interface` (MUST be translated)
**NOTE**: Do not include changes to this file in the generated commit message. It serves only as a system prompt to guide the message format.
Tedious but works.
1 Like
Any updates? I think this feature is very important !
Having the same issue for long
I’m having the same issue as well. Are there any updates about it? It would be nice to find it in the next update.
2 Likes
I’m experiencing the same issue. How is this still not fixed? We’re paying for this.
1 Like
Any updates yet?
Commit message AI: works with .cursorrules
The AI-generated commit message feature works with .cursorrules file
I wrote following instructions on .cursorrules
# Commit Message Rules
Commit messages are typically written in Korean.
Message must start with following headers
- **[Release]**: Major feature (e.g. project completion); use for the final commit when pushing to the main server.
- **[Making]**: Work in progress. Use when a Feat is not yet complete. Commits for temporary code storage.
- **[Feat]**: Feature
- **[Refactor]**: Code refactoring (code cleanup).
- **[UI]**: User interface.
- **[Bugfix]**: Bug fix. Use for fixes made after a Feat.
- **[Hotfix]**: Hotfix; for urgent changes when a detailed commit message is omitted.
- **[Docs]**: Documentation (e.g. dev docs, comments).
- **[I18n]**: Use for translation.
And it works
Tested on cursor version 2.4.28 windows
The reason it looks like it’s working is probably because Cursor learns from your git history. It’s just mimicking your previous commit style.
My commit history consists only of English and Korean, yet the AI provides responses in Polish whenever I instruct it to do so. This proves that it’s following the specific instructions in the .cursorrules file included in the prompt, rather than simply mimicking my past activity
// .cursorrules
## Commit Message Rules
### language
Commit messages are written in Język polski language.
### headers
Message must start with following headers
- **[Release]**: Major feature (e.g. project completion); use for the final commit when pushing to the main server.
- **[Making]**: Work in progress. Use when a Feat is not yet complete. Commits for temporary code storage.
- **[Feat]**: Feature
- **[Refactor]**: Code refactoring (code cleanup).
- **[UI]**: User interface.
- **[Bugfix]**: Bug fix. Use for fixes made after a Feat.
- **[Hotfix]**: Hotfix; for urgent changes when a detailed commit message is omitted.
- **[Docs]**: Documentation (e.g. dev docs, comments).
- **[I18n]**: Use for translation.
### description
after header and title, you should write description in Język polski with list format.
description must be specific and detailed.
### example
[Bugfix] Usunięcie zbędnego kodu z adaptera Port One
Usunięcie niepotrzebnych ciągów znaków (stringów) z sekcji obsługi błędów w adapterze Port One.
Poprawa czytelności kodu poprzez opakowanie funkcji pay.
Result
1 Like