Commit Messages

Write an evidence-backed Conventional Commit for one logical change.

1. Establish the evidence

Use the staged diff and facts the user supplied. Every type, scope, effect, issue number, and metric must trace to that evidence. If the change itself is missing, stop. Ask for the staged diff or a short summary of what changed. If only the motivation is missing, write the header and leave out the body.

2. Keep the commit atomic

One commit contains changes with one intent that should be reverted together. A fix and its focused regression test belong together. File count, directories, or multiple implementation types alone do not justify a split.