Show HN: acmsg (automated commit message generator)

I don't understand the reasoning for persisting LLM output that can be generated at any point. If I want to use an LLM to understand someone else's commits, I can use the LLM best suited for that task at the time I need the information, which will likely be more accurate than what was available at the time of the commit and will have access to more context.

I also believe that commit messages should focus on information the code doesn't already convey. Whatever the LLM can generate from looking at your code is likely not the info I'll seek when I read your commit message.

Maybe I am a bit old-fashioned but I think the commit message should convey intent and not content of the diffs. Perhaps the real utility of this is to describe existing commits in a repository.

When you are looking through commit messages, "Why?", Is the question you want answered. The diff contains "What?" and "How?".

Assuming that the commits in this repo were generated by this tool it is missing the "Why?".

This is worse than useless.

The commit message is supposed to contain the details that you can't just glance from the code. Why a certain decision was made, or the pro's and con's of a decision, a link to a relevant Github / Jira issue, etc.

I use the following script to allow copilot vim plugin to help me.

```plaintext name=../../bin/assisted-commit

#!/bin/bash

# Run git commit with --verbose --dry-run and save the output git commit --verbose --dry-run > ./commit.message

# Prepend # to every line and add "conventional commit message:" at the end sed -i 's/^/# /' ./commit.message echo "# uncommented conventional commit message using feat, fix or doc flags. !beakingchange iff change breaks backward compatibility:" >> ./commit.message echo "" >> ./commit.message

# Open the file in vim for editing, with cursor on a new line at the end and in insert mode vim +':normal Go' +startinsert ./commit.message

# Filter out commented lines and save to a temporary file grep -v '^#' ./commit.message > ./commit.message.filtered

# Commit using the filtered file git commit -F ./commit.message.filtered

# Delete the files rm ./commit.message ./commit.message.filtered

```

Don't forget to include committed code in the context when amending.

Looks like openrouter api can be self-hosted, which means you should be able to run this locally. If anyone is able to run this with ollama, please do post how you did that? :)

Just click the copilot button in any ide to generate an automated commit message in less than one second. This is effectively useless.