That’s the role of the commit title, with tags if you follow https://www.conventionalcommits.org/ standard.

99% of commit description will never be read. Only the title is usefull when you scroll to a git log.

But, for the remaining 1%, it means you ended up doing a git blame, git bisect or any funky stuff like this to troubleshot a bug. And when you find the commit that introduced the regression, written by some dude that leaved the company 5 years ago and see a description like “Add the whatever method in whatever class that do the stuff explained by the doc written in the file”… Well, thanks bro. But why did you do this !!!

A commit message is not supposed to be a summary of the code. It is supposed to gives information that you cannot deduct from the diff. Like:

• Is there an attached ticket ?
• Does it produce side effects ?
• Is it a quick and dirty fix just before the release ?
• What are the consequence of the modification ?
• Why you choose this approach instead of another ?
• Why are you not able to add regression test ? etc …

The first guy at Cursor that create the feature to generate commit message from diff is just a fucking moron that don’t understand the role of a commit message.