# Commit Messages

Git commit messages are a way to communicate change to fellow developers. To communicate change understanding context and why that change is necessary is important. We want all our repositories to have a commit log that is easy to consume and understand.

Please take a look at these seven rules for great git commit messages:

* [Separate subject from body with a blank line](https://chris.beams.io/posts/git-commit/#separate)
* [Limit the subject line to 50 characters](https://chris.beams.io/posts/git-commit/#limit-50)
* [Capitalize the subject line](https://chris.beams.io/posts/git-commit/#capitalize)
* [Do not end the subject line with a period](https://chris.beams.io/posts/git-commit/#end)
* [Use the imperative mood in the subject line](https://chris.beams.io/posts/git-commit/#imperative)
* [Wrap the body at 72 characters](https://chris.beams.io/posts/git-commit/#wrap-72)
* [Use the body to explain what and why vs. how](https://chris.beams.io/posts/git-commit/#why-not-how)

Before starting a new project discuss with the team and agree to a consistent commit message strategy.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://playbook.wednesday.is/engineering-playbook/release-and-delivery/commit-messages.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.