<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>git diff on Abbreviatory.com</title>
    <link>https://abbreviatory.com/tags/git-diff/</link>
    <description>Recent content in git diff on Abbreviatory.com</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 19 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://abbreviatory.com/tags/git-diff/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Abbreviatory 0.4 Reads Git Diffs, HTTP Responses and Directory Listings</title>
      <link>https://abbreviatory.com/abbreviatory-0.4-reads-git-diffs-http-responses-and-directory-listings/</link>
      <pubDate>Mon, 19 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://abbreviatory.com/abbreviatory-0.4-reads-git-diffs-http-responses-and-directory-listings/</guid>
      <description>Test runs and logs aren&amp;rsquo;t the only big outputs a coding agent reads. It reads diffs all day, to review what it changed. It calls APIs with curl and gets back a wall of JSON. It runs find to see what&amp;rsquo;s in a repository, and gets ten thousand paths. Abbreviatory v0.4.0 reads all three.
Each one gets rules of its own, because each one has its own idea of what matters.</description>
    </item>
    
    <item>
      <title>How to See the Shape of a Large Git Diff Before Reading Its Lines</title>
      <link>https://abbreviatory.com/how-to-see-the-shape-of-a-large-git-diff-before-reading-its-lines/</link>
      <pubDate>Mon, 19 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://abbreviatory.com/how-to-see-the-shape-of-a-large-git-diff-before-reading-its-lines/</guid>
      <description>Reviewing a big change starts with a question the diff doesn&amp;rsquo;t answer up front: what&amp;rsquo;s in here? git diff prints the first file&amp;rsquo;s first hunk and makes you scroll for the rest. A coding agent asked to review the same change reads all of it in order, and a 190 kB diff fills a good part of its context before it has seen the list of files.
The diff in this example is a real one, Abbreviatory&amp;rsquo;s own changes from v0.</description>
    </item>
    
  </channel>
</rss>
