# 2/10/2023 - CommitGPT

<figure><img src="https://user-images.githubusercontent.com/3975738/205517867-1e7533ae-a8e7-4c0d-afb6-d259635f3f9d.gif" alt=""><figcaption></figcaption></figure>

### Overview

Developers often find themselves coming up with meaningful commit messages to keep their version control accurate and informative. This helps in many ways: helping themselves by checking the commit history, helping other teammates identify changes and keeping the code properly identifiable and consistent. Commit messages are meant to describe code changes or references issues / bugs in which the new code includes the fix for.&#x20;

### Purpose

The purpose of **CommitGPT** is to handle the hard part for you. The 'hard part' of software engineering is documentation, commenting, and variable names. Everything else is easy. :smile:

CommitGPT will analyze the changes you made via a `git diff` and propose / suggest commit messages. Oftentimes, this is better than what us as developers can come up with.

### How is this beneficial to me as a developer?

As a developer, I often find myself questioning previous code and commits either I wrote, or another developer wrote. ***What did this commit include? Was this bug included in this code change?*** The list goes on...&#x20;

Although Albeit slower than committing a message of 'test' or 'stupid bug fixed', I can provide more meaningful messages such as: **"Bug Fix: Add null check across methods inside X Service"**&#x20;

&#x20;

### Resources

{% embed url="<https://github.com/RomanHotsiy/commitgpt>" %}
