I don’t get these kind of tools. A commit should be the why of a change, not a summary of what it is, anyone can either get that themselves or just read the code if they desire. What you can not get from the code is the _why_ which only you as the author can put. Show 3 replies

There's three types of people: those who already write excellent commit messages explaining the why, those who write decent ones explaining the what, and those who write garbage commit messages. Empirically, the first set is small. This tool will help the middle type be more efficient, and help the last type drastically.

Well done OP.

Neat project. If you're looking for something simpler just to use w/ Claude Code, a simple call to "claude -p" can work: https://github.com/nicksergeant/dotfiles/blob/master/zshrc#L... Show 1 reply

Here's the 20 line bash version I whipped up a while back cuz yes lazy about writing good commit messages.

Supports claude and gemini with model selection and goes into the githook such that when you type `git commit` it invokes and generates the message.

https://gist.github.com/torqu3e/c08f4aa4e80fba66dce6c35d63dd...

Chiming in with my alternative, like others' but uses simonw's `llm`:

    git upstream-diff | llm --system-fragment cl-description.md

However, in practice, I notice the generated messages focus more on the what than the why. So it's rare I use them verbatim.

I've been using LMStudio to run a local LLM (Qwen3-4B) to generate commit messages using this command:

```

git diff --staged --diff-filter=ACMRTUXB | jq -Rs --arg prompt 'You are an assistant that writes concise, conventional commit messages. Always start with one of these verbs: feat, fix, chore, docs, style, refactor, test, perf. Write a short!! message describing the following diff:' '{model:"qwen/qwen3-4b-2507", input:($prompt + "\n\n" + .)}' | curl -s http://localhost:1234/v1/responses -H "Content-Type: application/json" -d @- | jq -r ".output[0].content[0].text"

```

Hey all - disclaimer I'm one of Cell's friends and encouraged them to release their utility on Pypi for others. It quickly became one of my favorite tools that I use every day.

`git commit` is gone, `uvx gac` is in!

"gac" is giving me PTSD flashbacks from having to deal with the "Global Assembly Cache" aeons ago.

> Automatic secret detection: Scans for API keys, passwords, and tokens before committing

Surely this is done on-device right? Or is the prompt asking the LLM if there are secrets in the changes.

Arguably I trust Github / Gitlab / etc more than OpenAI / Anthropic / etc

Show 1 reply

I like that you’ve added secret detection and multi-provider support — that’s something most LLM commit tools miss. Have you benchmarked latency differences between local models (like Ollama) and OpenAI/Anthropic? Would be interesting to see a speed comparison.

Maybe it's because these days I use perforce more than git but I tend to find myself writing 80% of my commit message before I write any code and touch it up a little at the end.

I like the lazycommit+lazygit combo.

https://github.com/m7medVision/lazycommit

Oh nice. Man I hate filling out all that stuff. And getting the LLM to do it without freestyling and hallucinating is a pain. Kinda wish it were an MCP so I can shove it in my CLI or maybe the hooks for git... Show 1 reply

Hate writing commit messages.

Just installed gac; they nailed the UI/UX.

And so far, it works quite well.

Show 1 reply

Very neat little project, I look forward to trying this

aicommit2 works great: https://github.com/tak-bro/aicommit2

Getting started is as easy as installing claude/codex/gemini: npm install -g aicommit2

I'm excited to give gac a try and see how it stacks up! The steering hints with gac might give it an edge.

Your scientists were so preoccupied with whether or not they could, they didn't stop to think if they should. Show 1 reply

This misses the point of what a good commit message is so much that it could be a delightful satire. Show 1 reply