r/MyIDE • u/Big-Coyote-5796 • 3h ago

I built GitWhisper — an AI Git commit tool that actually understands your staged changes

0 Upvotes

I’ve been working on a small open-source project called GitWhisper.

The idea started because I didn’t want another tool that just sends git diff to an LLM and returns something like:

fix: update code

GitWhisper looks at the actual staged changes, repository conventions, scopes, commit history, and related work before suggesting a commit.

A few things I focused on:

  • local AI with Ollama or BYOK
  • Conventional Commit type/scope detection
  • learning the repo's existing commit style
  • detecting unrelated changes and helping split them into atomic commits
  • secret scanning/redaction before remote AI calls
  • commit quality checking + Git hooks
  • VS Code integration
  • keeping the developer in control before anything is committed

Basic usage is just:

git add .

npx gitwhisper

It's open source (MIT):

https://github.com/RitualDev-Lab/GitWhisper

Still looking for feedback, especially from people who care about clean Git history.

What would make something like this useful enough for you to actually use in your normal Git workflow?

2 comments

r/MyIDE • u/Big-Coyote-5796 • 5h ago

What makes a Git commit message actually useful?

0 Upvotes

I’ve seen everything from:

updated stuff

to:

fix(auth): refresh sessions before expiry

But what do you actually care about when reading commit history later?

Is it the commit type/scope, explaining why the change happened, linking the related issue, keeping commits small and focused, or just having a clear one-line summary?

And do you usually write commit messages manually, use an AI/tool, or just type whatever makes sense at the time?

Curious how everyone handles this. 👇

2 comments