If you've ever dug through your own git log and cringed at messages like "fix", "more tests", or the classic "cleanup.", you're not alone. Developer gemyago recently published a practical solution on DEV.to that tackles this exact problem using two simple AI prompt files.

The Commit Message Problem Is Bigger Than You Think

The author admits their pull requests used to contain dozens, sometimes hundreds, of commits with messages that conveyed absolutely nothing useful. "Most of the messages were complete garbage: Cleanup., More tests., fix., some initial notes," gemyago writes. This isn't just a personal embarrassment issue—messing up your commit history makes code reviews painful, debugging harder, and onboarding new developers a nightmare.

Two Small Markdown Files, Zero Friction

The solution centers on two lightweight prompt files that integrate directly into a developer workflow. The first file, commit.md, handles staging changes, reading the staged diff, and generating an appropriate commit message based on what's actually being changed. Rather than wrestling with git add -p or staring at a blank terminal wondering what to write, developers simply run their AI tool of choice against these prompts.

How the Workflow Actually Works

The beauty here is simplicity. When you stage your changes and invoke the prompt, it reads what's actually in the staging area—not vague intentions, but real code differences. The AI then generates a commit message that accurately describes those specific changes. No more "wip" commits pushed at 2am or generic "update" messages that tell future-you absolutely nothing.

Beyond Just Commit Messages

The approach speaks to a broader shift in how developers are using AI tools—not for flashy demos, but for the tedious daily tasks that slow down real work. Writing good commit messages is boring. It's also important. Automating it with well-crafted prompts removes the friction that causes developers to just type whatever's fastest.

Key Takeaways

  • Generic "fix" and "cleanup" commits destroy your project's history readability over time
  • Two strategically crafted Markdown prompt files can automate meaningful commit message generation
  • Staging changes first ensures AI generates messages based on actual code differences, not vague intentions
  • This pattern—small prompts for boring tasks—represents practical AI tooling that developers actually want

The Bottom Line

This isn't revolutionary tech. It's two text files solving a daily annoyance that every developer faces. That's exactly the kind of infrastructure improvement we should be building more of—novel applications get headlines, but boring solutions that actually work get adopted.