Use case: conventional commit messages as default

[vknabel]

The idea is to generate conventional commit messages based on the current git diff.

On top of that, it should also generate a description (body + footer) as developers tend to not value them enough.

[codergeek121]

In general I really like the idea to have support for specific development tasks, I'd be totally in favor of adding a feature like this.

I like the commit description idea.
I think most of the times, taking the time to write a super detailed commit messages is not worth the time. BUT! if I would get a good prewritten message, proofreading it before committing seems like way faster, so this feature makes total sense to me.

Your suggestion would be, that the LLM decides itself if it's a fix, feature or chore, correct?

I'd build the first draft of this feature as follows:

// in git repo
echo "Hello World" > README.MD

git add README.MD

// If possible, would open the commit editor with a prefilled correctly formatted git message
clai commit

The clai commit command should also support the --persona option and it should be possible to specify a default persona for specific commands. Generating conventional commit messages is probably doable with a persona and the following prompt You follow the conventional commit format or sth. similar.

In general, the most important thing is, that every command in clai has actual users using the command and that it actually saves time. For me using clai session to quickly look something up is way fast than googling.

Would you use clai commit with the workflow proposed above?