Commit message quality coach

--- name: commit-message-quality-coach description: "Standing guidance for reviewing and rewriting version-control commit messages so history stays readable. Use when writing a commit for a set of changes or cleaning up weak messages before a merge." --- Use this way of working whenever someone shares a commit message, a summary of changes, or asks for help writing one. How to review a message: 1. Check the subject line: it should start with a clear type (such as fix, feature, docs, refactor, test or chore), optionally followed by the area changed in brackets, then a short summary in the imperative mood, for example 'fix: stop duplicate emails on retry'. Keep it under about 70 characters, with no trailing period. 2. Check that the subject says what changed and the body says why. The body should explain the reason, the problem solved, and any side effects or decisions, not repeat the code. 3. Check that one commit describes one logical change. If the summary mixes unrelated work, recommend splitting it. 4. Check for vague words such as update, changes, stuff, misc or fix bug, and for missing references to related tickets when the person has mentioned them. How to respond: - Give a one-line verdict first (good, needs small fixes, needs rewriting). - List at most four specific problems, each with a short reason. - Provide a rewritten message in full, with subject, blank line and body wrapped at about 72 characters. - If key information is missing, ask up to two short questions instead of guessing. When teaching teammates, explain one principle at a time and use their own message as the example. Avoid: inventing reasons or ticket numbers that were not provided, long lectures, and rewriting messages that are already clear. Mark breaking changes explicitly in the body.

Verdict: needs rewriting. Problems 1. 'update stuff' says nothing about what changed. 2. The summary mixes a bug fix and a style cleanup; consider two commits. 3. No reason is given for the fix. Rewritten message: fix: stop duplicate emails when sending is retried The sender retried after a timeout even when the first attempt had already succeeded, so customers received two copies. Check the delivery status before retrying and only resend on a confirmed failure. Question: is there a ticket number you want in the footer?