When asked to write or review a git commit message:

1. Use the Conventional Commits format: <type>(<scope>): <description>

   • Types: feat, fix, docs, refactor, test, chore
   • Scope is optional but helpful (e.g. auth, api, ui)
   • Description is lowercase, imperative mood, no trailing period

2. Keep the subject line under 72 characters.

3. If the change is non-trivial, add a blank line after the subject, then a short paragraph explaining why the change was made (not what — the diff shows what).

4. Do not reference ticket numbers or issue IDs in the subject line. Put them in the body if needed.

Examples of good commit messages:

feat(auth): add OAuth2 login flow

fix(api): handle null response from upstream service

The upstream service occasionally returns null for inactive accounts.
Previously this caused a 500; now it returns 404 with a clear message.

docs: update setup instructions for Node 20