feat: Implement AI-powered commit message generation

[ammmze]

Adds support for using AI to generate commit messages via the describe-commit tool, enhancing commit clarity and detail. This feature is configurable via .env variables.

see: describe-commit

This feature would be completely optional, and disabled by default.

Here are the last few commits that were generated while testing this functionality. I tested using gemini with the default gemini model (gemini-2.0-flash).

[Staubgeborener]

Pretty interesting. Please rename the variable to something like ai_describe_commit or ai_commit.
Is it possible to use this with ollama? If yes, can you explain how?

[Staubgeborener]

I would also remove describe_commit completely. We don't need a variable to set it to true or false. It would be sufficient to just use describe_commit_args. As soon as there is something in it, it is used with the corresponding argument. If there is nothing in it, then it is not used. Or am I missing something? This can also be adjusted accordingly.

[ammmze]

Pretty interesting. Please rename the variable to something like ai_describe_commit or ai_commit.

Sounds good! I'll use ai_describe_commit.

I would also remove describe_commit completely. We don't need a variable to set it to true or false. It would be sufficient to just use describe_commit_args. As soon as there is something in it, it is used with the corresponding argument. If there is nothing in it, then it is not used. Or am I missing something? This can also be adjusted accordingly.

The describe-commit project by default supports reading from a config file (~/.configs/describe-commit.yml on Linux) where the ai provider and api key could be configured. In that case no args would be required when invoking describe-commit.

Is it possible to use this with ollama? If yes, can you explain how?

Looks like the describe-commit cli doesn't currently support Ollama and doesn't currently allow for setting a custom url for OpenAI (which many providers support). I've opened a feature request to allow setting a url for the OpenAI provider.

There are other options out there (aicommit, commitai, git-ai-commit...though doesn't support gemini, which is what i'm using currently), though most of them have some certain python dependencies vs describe-commit which is just a single binary that you would need to install.

[Staubgeborener]

Ok, in this case, we only use describe-commit from the project. But we still need to rename it in this project, so the users can simply see, that this has something to do with AI. Also, after your explanation, i would still remove the boolean. We don't support the ~/.configs/describe-commit.yml config file and keep it simple.

After finishing this, please open a new PR here and change the FAQ accordingly with this feature.