Rules for "Generate commit message"
keshen
definitely need this. and i'd like to add that instead of generating a commit message, this feature could be "refine my commit message", because i prefer to write a short imperative summary by myself and then ask ai to generate a body
0x4e32.dev
I will also add this one here.
The generated commit message should be based on "STAGED" changes.
In my screenshot, you can see that I've only staged the settings.json file, which is not included in the deployment guide.
t
trynewaithings
I noticed that when a commit message is generated, it uses all changes as context to generate the commit message, can you please make it take only the added changes as context (not ALL changes).
t
truevox744
Yes, I was surprised since this is gated to only paying users, once I paid it was so lackluster. It should recognize previous commit style, and it should take direct instruction. Glad to see it's in progress - can't wait 'till it gets a bit more polish, then I can stop swapping IDEs every time I wanna commit lol.
0x4e32.dev
The "generate commit message" should be smart enough to know your commit message format. Cursor does this.
G
Gerhard Gmail
I put those in my gloabl windsurf rules and it works for me
D
Dom De Chiera
Gerhard Gmail yes now the model just has to follow the rules 🤣 doesn't work every time. Global rules seem to be followed even less than local rules. Just another example of the unreliability of models. Same for MCP servers with guidelines, picks and chooses when to follow.
All my commit messages in a project have been Conventional Commits format but generate just does a standard commit message. So, it definitely does not follow your past commit conventions.
Tony Dehnke
Gerhard Gmail Do you have a format or example of what has worked for you that you could share? It doesn't seem to follow rules well
ghoti
Gerhard Gmail May I ask for an example on what you put on global rules? No matter what I try it still doesn't follow conventional commits despite giving examples in global rules files.
G
Gerhard Gmail
ghoti Tony Dehnke
## Git Conventional Commit
CRITICAL: Always use common conventional commit types:
- feat
- fix
- docs
- style
- refactor
- test
- chore
But I noticed this is only working in the Cascade Chat, not with the new Generate Commit Message Feature.
So yes, they need to amend this.
ghoti
Gerhard Gmail ahh ok. I'm honestly surprised that this wasn't thought out.
With Cursor, I didn't even need to tell it to follow Conventional Commits. I think it just used my previous commits as part of the context and it just followed it everytime.
M.K.
This is an absolute must in my opinion.