Generate Commit Message Generate too much

Discussion
1

I like the new feature where we can now generate commit messages on the UI. But right now it generates way too much information about the changes.

2

Can you post a screen of what youre seeing (That can be shared) - so those of us who havent used that feature yet can grok what that behavior looks like?

3

Hey, can you add this line to your rules: “For commit messages, keep them super short and concise. Just a couple of sentences max.” This should help.

2 Likes
4

fwiw, I asked cursor to make some rules for .cursorrules in the hopes that they do help :slight_smile:

Commit Message Guidelines

  • Write commit messages for a non-technical audience
  • Keep messages concise and clear, avoiding technical jargon
  • Focus on the business impact or user-facing changes
  • Use simple, active voice
  • Break multiple changes into separate bullet points
  • Avoid technical details like package names or implementation specifics

Examples:
:white_check_mark: Good:

  • Added notifications for when the site updates
  • Improved how the site appears when shared on social media
  • Fixed the contact form submission error

:x: Avoid:

  • Enhanced environment configuration and layout metadata
  • Updated OpenGraph meta tags in app/layout.tsx
  • Implemented Vercel webhook integration with SHA handling

My particular circumstance, but that’s the point - we all have our quirks.

1 Like