I agree, for the most part. Periods are unnecessary, though (and may be used for purposes other than ending a sentence, which usually ends with - well - nothing else.)
Capitalizing nothing but the first word of the commit is asinine, since I've seen tons of commits with abbreviations, such as "UI" (or my JIRA issue numbers - like the one below) , and even "camelCase" functions named within them (since those will not be listed as files changed, but are inside of the actual files.)
However, one thing I completely agree with is the issue number. A recent commit of mine was:
[CORE-14] Added login validation
If it wasn't a personal project, I would still be recommending that the issue number goes first - as should should anything that categorizes/labels the commit. However, in a team-based environment, an imperative/present tense summary (with an abbreviated type) is more precise, like:
[CORE-14] feat: add login validation
But, then again, it usually is a decision we can't make ourselves, and we must be adaptable according to who we're working with and where.