Thank you so much for the time and effort to bringing these points to my attention,

I've made the necessary adjustments as per your feedback.

But, regarding Rule 6, the preference for present-tense, imperative-style commit messages comes from git itself. According to Git, the objective is to inform others about what the commit will achieve, rather than detailing what you did.

Moreover, if you examine your repository history, you'll notice that Git-generated messages adhere to this tense: “Merge” not “Merged”, “Rebase” not “Rebased” so writing in the same tense keeps things consistent, especially when working with a team.

It feels strange at first but it does make sense.