[rinchik]

Isn't wording a bit off? "scope" should describe what the commit DOES, not what you are personally DOING, and not what you were intended to DO.

"body", optionally, describes WHY.

Also it feels like more of a convention for a personal project with optional C(I|D) automation prerequisites. In a team there should be a clear and emphasized place for the issue tracking info (ticket number, task id etc etc)

[GordonS]

I quite like the idea of `scope` for large, multi-component projects, so you can tell instantly from the commit message what component has been changed.