# Writing good commit messages {% hint style="info" %} This process was written a long time ago and is due for review. It's been left here in case it's useful to you, but a different approach may apply for your projects. {% endhint %} This is a guide to writing better commit messages in order to help maintain the git logs, and provide better information for future debugging and development. Follow the link below to see the slidedeck outlining this process. {% embed url="" %} [![Creative Commons Licence](https://i.creativecommons.org/l/by-sa/4.0/88x31.png)](http://creativecommons.org/licenses/by-sa/4.0/)\ This work is licensed under a [Creative Commons Attribution-ShareAlike 4.0 International License](http://creativecommons.org/licenses/by-sa/4.0/). --- # 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://dxtech.tpximpact.com/best-practice/git-commit-messages.md?ask= ``` 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.