Cursor commit message generation

Feature Requests
1

Feature request for product/service

Cursor IDE

Describe the request

Flow:

  1. The user writes a general rule for generating commits
  2. The user can write a project rule for generating commits. There is a check mark for “override (general rule)”.
  3. The user selects the model used to generate commits (I like Gemini 2.5 Flash Thinking)
  4. The user clicks the generate button (as they are now).
  5. The generator gets commit rules and something like git diff && git add . && git status
  6. This generation is counted as a separate request.

What we get

  1. Style control.
  2. The ability to correctly generate messages for commits with large changes.
1 Like
2

Clarification: now it is possible to stage several files from all of them and a message will be generated only for them - it is necessary to preserve this behavior.