Your Commit Tool Doesn't Read Your Code. Mine Does.
I have unreasonably high standards for commit messages. That's not a brag — it's a diagnosis. I'll rewrite a subject line four times before even considering pushing. I'll agonize over whether somet...

Source: DEV Community
I have unreasonably high standards for commit messages. That's not a brag — it's a diagnosis. I'll rewrite a subject line four times before even considering pushing. I'll agonize over whether something is a refactor or a feat. I've more than once spent longer on a commit message than on the code it described. So naturally, when AI commit message generators became a thing, I tried them all. Every single one does the same thing: take git diff, throw it at an LLM, hope something plausible comes back. And every single one produces something like this: refactor: update code and improve things That's not a commit message. That's a cry for help. 🤯 The Problem Nobody Is Solving Here's what happens when you send a raw diff to an LLM: -pub fn validate(input: &str) -> bool { +pub fn validate(input: &str, strict: bool) -> Result<()> { You and I see this instantly: new parameter, changed return type, breaking change. An LLM sees two lines that are kinda similar and one has more