Guide for writing git commit titles and messages following Conventional Commits format with session context
Use this skill when writing git commit messages. These conventions apply to all commits regardless of how they are created (explicit commands, ad-hoc requests, or any other workflow).
The git author for commits is always:
Mitchell Nielsen[email protected]Do not look up git user config. Use these values directly.
git commit --no-verify. Fix hook errors instead.Follow the Conventional Commits format.
<type>(<scope>): <description>
Run git log -n 50 --pretty=format:%s to see commonly used scopes in
the current repository. Match existing conventions.
Examples:
docs: correct spelling of CHANGELOGfeat(api): send an email to the customer when a product is shippedfix(auth): handle expired tokens on refreshCloses #1234 or Closes ENG-1234.Include a brief summary of the development session that produced the changes. Focus on context a reviewer would not get from reading the code:
.env,
credentials.json, etc). Warn the user if they specifically
request to commit those files.feat(ingest): add retry logic for transient upstream failures
Upstream API started returning 503s intermittently after their
maintenance window. Added exponential backoff with jitter capped
at 30s. Considered circuit-breaker but the failure rate is too
low to justify the complexity.
Closes ENG-4521