OpenClaw LaunchOpenClaw Launch
✍️

Commit Message Convention

Verified

by Community

Establishes conventions for writing meaningful commit messages. Covers the anatomy of a good commit message, imperative mood, subject line limits, body formatting, and how commit messages support code review and changelog generation.

gitcommit-messagesconventions

Commit Message Convention

Write commit messages that clearly communicate what changed and why. Good commit messages make code review easier, debugging faster, and changelogs more useful.

Usage

Ask about commit message formats, establishing team conventions, or improving your commit history readability.

Examples

  • "What format should I use for commit messages?"
  • "How do I write a good commit message body?"
  • "Should we enforce commit message conventions in CI?"

Guidelines

  • Use the imperative mood in the subject line: "Add feature" not "Added feature"
  • Keep the subject line under 50 characters, the body under 72 characters per line
  • Separate the subject from body with a blank line
  • Explain what and why in the body, not how — the code shows how
  • Reference issue numbers for traceability

More Git & Version Control Skills

🪝
Git Hooks Guide

Automate quality checks with client-side and server-side Git hooks.

📏
Git Rebase Workflow

Use Git rebase to maintain a clean, linear commit history.

🔎
Git Bisect Guide

Find the commit that introduced a bug using binary search.

📦
Monorepo Setup Guide

Set up and manage a monorepo with proper tooling.