I know there are lots of these, but this one is my no-frills CLI tool for generating conventional commits from whatever is staged. It's super small, super fast, super fun.
Nice tool. To add a workflow to the 'lots of these', I usually use an aichat[^1] role. The prompt is stored in `~/.config/aichat/roles/gitcommit.md` and then I do this:
I like that your tool includes some previous commit messages... I'm not sure if that can be done with `aichat` but it seems like a great idea.
I'd be tempted to wrap individual commit messages in pseudo-xml <commit> tags, as Claude really likes those[^2] and the `%B` format doesn't really show the breaks between commit messages.
depends what you're doing. If you're using ChatGPT via the UI for a one off question, sure. If you're prompting an LLM that is doing a critical task in production millions of times, minor improvements can have significant benefit
I have done the latter much more than the former. My experience has been the issues come from inputs that you don’t foresee, not reliability on in-distribution uses (which would be your “training” data for prompt optimization). And the worry is that this kind of optimization would lead to substantive revisions of the guidelines set out in the prompt, which could further compromise performance out of distribution.
To the extent that you need to eke out reliability on the margins, one is vastly better served by actual fine-tuning, which is available both for open-source models and most major proprietary models.
git add .
commit
a (to accept, e to open Vim to edit, r to reject)
Conventional commits for everyone!
<3