<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Alan Shabrandi</title>
    <description>The latest articles on DEV Community by Alan Shabrandi (@alan_shabrandi).</description>
    <link>https://dev.to/alan_shabrandi</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2628350%2Ff8f877d7-7d26-44e0-b718-a461c9a52db4.jpeg</url>
      <title>DEV Community: Alan Shabrandi</title>
      <link>https://dev.to/alan_shabrandi</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/alan_shabrandi"/>
    <language>en</language>
    <item>
      <title>How I Built Scribe: A Fast, Local-First AI Commit Generator in Go</title>
      <dc:creator>Alan Shabrandi</dc:creator>
      <pubDate>Thu, 30 Jul 2026 16:38:02 +0000</pubDate>
      <link>https://dev.to/alan_shabrandi/how-i-built-scribe-a-fast-local-first-ai-commit-generator-in-go-4a4h</link>
      <guid>https://dev.to/alan_shabrandi/how-i-built-scribe-a-fast-local-first-ai-commit-generator-in-go-4a4h</guid>
      <description>&lt;p&gt;Every day at the end of coding sessions, I got lazy with my git commits—writing things like "wip", "fix stuff", or "changes". Existing AI commit tools either felt too heavy, lacked speed, or forced sending git diffs to third-party cloud APIs.&lt;/p&gt;

&lt;p&gt;So I built &lt;strong&gt;Scribe&lt;/strong&gt;—a lightweight, fast tool written in Go that generates Conventional Commit messages using local LLMs (Ollama) or optional cloud models.&lt;/p&gt;




&lt;h3&gt;
  
  
  🎥 Quick Demo
&lt;/h3&gt;

&lt;h4&gt;
  
  
  1. VS Code Extension
&lt;/h4&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcq21s731wq2oo7lj1j10.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcq21s731wq2oo7lj1j10.gif" alt="Scribe VS Code Extension Demo" width="800" height="209"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h4&gt;
  
  
  2. Terminal &amp;amp; CLI Tool
&lt;/h4&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgot51tp5h2gu5een7x74.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgot51tp5h2gu5een7x74.gif" alt="Scribe CLI Demo" width="721" height="216"&gt;&lt;/a&gt;&lt;/p&gt;




&lt;h3&gt;
  
  
  🚀 Key Features
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Local-First &amp;amp; Private:&lt;/strong&gt; Native integration with Ollama—your diffs stay on your machine.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;High Performance:&lt;/strong&gt; Built with Go for near-instant execution.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Smart SHA-256 Caching:&lt;/strong&gt; Hashes staged diffs to avoid wasteful LLM calls.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Dual Interface:&lt;/strong&gt; Use it directly as a CLI tool or through the native VS Code extension.&lt;/li&gt;
&lt;/ul&gt;




&lt;h3&gt;
  
  
  🛠️ How It Works (Under the Hood)
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Staged Diff Extraction:&lt;/strong&gt; Reads your staged changes via Git.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;SHA-256 Hashing:&lt;/strong&gt; Checks if the diff was already processed to save time and system resources.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Prompt Engineering:&lt;/strong&gt; Passes the diff context to Ollama (or API) with a tuned prompt for Conventional Commits format (&lt;code&gt;feat:&lt;/code&gt;, &lt;code&gt;fix:&lt;/code&gt;, &lt;code&gt;refactor:&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Native Integration:&lt;/strong&gt; Drops the generated text right into the VS Code Source Control input box or outputs it to the terminal.&lt;/li&gt;
&lt;/ol&gt;




&lt;h3&gt;
  
  
  📦 Try It Out &amp;amp; Contribute
&lt;/h3&gt;

&lt;p&gt;Scribe is 100% open-source, and I’d love to get feedback, feature requests, or contributions from the community!&lt;/p&gt;

&lt;h3&gt;
  
  
  🔗 Repository &amp;amp; Extension Links
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Core &amp;amp; CLI Tool (Go):&lt;/strong&gt; &lt;a href="https://github.com/alan-shabrandi/scribe" rel="noopener noreferrer"&gt;github.com/alan-shabrandi/scribe&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;VS Code Extension:&lt;/strong&gt; &lt;a href="https://marketplace.visualstudio.com/items?itemName=alan-shabrandi.scribe-vscode" rel="noopener noreferrer"&gt;marketplace.visualstudio.com/items?itemName=alan-shabrandi.scribe-vscode&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you find it useful, feel free to drop a ⭐ on GitHub or leave a review on the marketplace. What does your current commit workflow look like? Let me know in the comments below!&lt;/p&gt;

</description>
      <category>go</category>
      <category>vscode</category>
      <category>ai</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
