One of my favorite posts ever written came out nearly ten years ago. And it wasn't about tech. It was about communication:

How to Write a Git Commit Message
Commit messages matter. Here’s how to write them well.

The post lays out seven simple rules to format git commit messages so that other git commands become infinitely more useful. After discovering it, I took its rules to heart and enforced better coding standards among my teams. As a result, I'd like to think that I mastered git and improved the efficiency of my colleagues.

I've since learned about other equally-strong standards for writing commit messages. The format I see used most commonly in the wild is the semantic commit message:

Semantic Commit Messages
See how a minor change to your Git commit message style can make you a better programmer.

On occasion, I'll also see its variant, the conventional commit message:

Conventional Commits
A specification for adding human and machine readable meaning to commit messages

And I have no doubt that plenty of other standards for commit messages exist. Most will be sufficiently-good choices, so just pick one and stick to it! At the end of the day, the consistency of using only one format for commit messages is more important than the specific format itself. Trust me, your collaborators will thank you heartily.