There’s a community standard out there called Conventional Commit for structured git-commit messages. If you don’t know about it already, it recommends a strict type(scope?): description format for describing a code change in a repo.
Idea being that you front load the important stuff, so if you only read e.g. the first 5 lines, you don’t miss anything important later on, you can only “refine” the information you’ve already received.
I’ve seen people suggest using the inverted pyramid method style that journalists use.
https://en.wikipedia.org/wiki/Inverted_pyramid_(journalism)
Idea being that you front load the important stuff, so if you only read e.g. the first 5 lines, you don’t miss anything important later on, you can only “refine” the information you’ve already received.