Reading articles like this, and remember my teams just uses the poorly written issue name in the commit message, branch name, and even PR title.

Oh my, I've seen commit messages like that, but did not know this was some pseudo-standard.

I really can't stand such standards. The standard's webpage has a good example:

chore!: drop support for Node 6

• Apparently, any developer is supposed to know that '!' indicates a breaking change.
• Apparently, a 'chore' may contain a breaking change.

Within that standard, I guess that's obvious. It's a chore, because it's neither a feature nor a fix.
But not knowing that standard, I figured a 'chore' is some boring task with no larger consequences. Skimming through the commit log, I might have even skipped reading the whole commit message, because of that prefix.

Author here. Thanks for posting.

I might come up with another of these posts soon "I hate squash merges" :-P