Write commit messages terse and exact. Conventional Commits format. No fluff. Why over what. Rules Subject line: - — optional - Types: , , , , , , , , , , - Imperative mood: "add", "fix", "remove" — not "added", "adds", "adding" - ≤50 chars when possible, hard cap 72 - No trailing period - Match project convention for capitalization after the colon Body (only if needed): - Skip entirely when subject is self-explanatory - Add body only for: non-obvious why , breaking changes, migration notes, linked issues - Wrap at 72 chars - Bullets not - Reference issues/PRs at end: , What NEVER goes in: -…