AI-generated commit message

Ideas Feature Requests
21

Hi there. Maybe this video can help with configuring a standard for commit messages. It has a link to a GIST that is useful.

22

Hello!
While there is a command to automatically generate commit messages, it only works within the source control panel. I frequently use the “Commit all” command shortcut to quickly create commits without switching between side panels.

However, when the commit dialog box opens, there’s no option to automatically generate a commit message. I’d like to have this auto-generate feature available in the commit dialog as well.

23

I’m running version 0.44.11 and building a codebase using dev containers. All of a sudden, the Aji generaqted commit message feature (the sparkle icon next to the commit message input) no longer works when in the dev container. but if I leave the container, it works again. So that means that I have to reopen the folder locally, stage the files, and then hit the sparkle icon and then commit. Then I reopen the container and start worjgain, where chat, composser, etc continue to work, but the soaqrkle icon doesn’t…

Please help!

24

Hey, we should have some stability improvements for DevContainers coming in our next update very soon, which may resolve this issue!

25

need this feature!

26

Hey, this feature is already available in Cursor, but may have some issues if being using inside a DevContainer. We are hoping our next release may fix this!

27

I do the same thing. I tell the composer agent to look over @commit and make the commit in the terminal. Here’s my prompt that I use for Git changes.

–

You will analyze the @Commit and perform the following tasks:

  1. Generate a detailed and easy-to-read git summary of the changes made in the diff.
  2. Write a commit message that follows these best practices:
    • :bulb: Use a clear, imperative subject line (e.g., “Add feature” or “Fix bug”).
    • :memo: Keep the subject line concise (50 characters or less).
    • :scissors: Separate the subject from the body with a blank line.
    • :clipboard: Use bullet points in the body for listing changes.
    • :books: Include a short “why” explanation to give context.

For example:
:sparkles: refactor: improve deployment configuration and type safety

  • Configure Vercel to exclude unnecessary files:
    • Add excludeFiles pattern in vercel.json.
  • Update ESLint to skip test files:
    • Add ignorePatterns to .eslintrc.json.
  • Enhance type safety:
    • Replace any with type unions in useCursorPagination.
    • Add NodeData and RuleNode interfaces.
  • Add JSDoc for key functions.

  1. Use PowerShell commands to stage and commit the changes:
    git add . ; git commit -m ":sparkles: refactor: improve deployment configuration and type safety n`

    • Configure Vercel deployment to exclude test files. n- Update ESLint rules. n- Enhance type safety. n- Add JSDoc documentation."`

  2. :dart: Confirm the commit was successfully executed.

Keep it clean, clear, and to the point!

28

The commit message generator generates pretty weak commit messages, far worse than if I just ask composer “generate a commit message for this diff”. Not sure what LLM its using or old prompt, but would be very awesome if someone could take a few minutes and update it :slight_smile: