Hi Imani, thanks for sharing your experience with us! When I started using git, I was the same way when creating my commit messages.
I did mostly to save progress or bundle all the changes to have one commit. After getting more involved in the dev community and discovering resources. I was able to discover The seven rules of a great Git commit message. This convention has similar rules to your specs. If you really want to enforce these rules, you can create a template as well as git hook so it won't let you commit unless it meets the criteria you set.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.