<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Developer Tools - Tag - vo.rs</title><link>https://vo.rs/tags/developer-tools/</link><description>Developer Tools - Tag - vo.rs</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Sat, 14 Jun 2025 14:00:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/developer-tools/" rel="self" type="application/rss+xml"/><item><title>AI-Powered Git Commit Messages: Useful or Just Annoying</title><link>https://vo.rs/story/ai-powered-git-commit-messages-useful-or-just-annoying/</link><description>&lt;p&gt;There&amp;rsquo;s a particular flavour of laziness that git commit messages bring out in people. You&amp;rsquo;ve just spent an hour on a fiddly change, the work is done, and now a text editor opens demanding you explain yourself. So you type &amp;ldquo;fix stuff&amp;rdquo; and move on, and three months later you&amp;rsquo;re spelunking through &lt;code&gt;git log&lt;/code&gt; cursing your past self. The pitch for AI commit messages is simple: feed the staged diff to a model, get back a tidy conventional-commit summary, accept it, done. I&amp;rsquo;ve been running this on my own repos for a while. It&amp;rsquo;s genuinely useful and quietly dangerous, and which one depends entirely on how you wire it up.&lt;/p&gt;</description><pubDate>Sat, 14 Jun 2025 14:00:00 +0000</pubDate></item></channel></rss>