<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Workflow on Parikshit Agnihotry</title>
    <link>https://p.agnihotry.com/tags/workflow/</link>
    <description>Recent content in Workflow on Parikshit Agnihotry</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 23 Apr 2026 00:00:00 -0700</lastBuildDate>
    <atom:link href="https://p.agnihotry.com/tags/workflow/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Two AIs, One PR: An Adversarial Code Review Loop</title>
      <link>https://p.agnihotry.com/post/two-ais-one-pr-adversarial-code-review-loop/</link>
      <pubDate>Thu, 23 Apr 2026 00:00:00 -0700</pubDate>
      <guid>https://p.agnihotry.com/post/two-ais-one-pr-adversarial-code-review-loop/</guid>
      <description>&lt;link rel=&#34;stylesheet&#34; href=&#34;https://p.agnihotry.com/css/hugo-easy-gallery.css&#34; /&gt;&#xA;&lt;div class=&#34;box&#34; &gt;&#xA;  &lt;figure  itemprop=&#34;associatedMedia&#34; itemscope itemtype=&#34;http://schema.org/ImageObject&#34;&gt;&#xA;    &lt;div class=&#34;img&#34;&gt;&#xA;      &lt;img itemprop=&#34;thumbnail&#34; src=&#34;https://p.agnihotry.com/images/two-ais-one-pr-adversarial-code-review-loop.webp&#34; alt=&#34;/images/two-ais-one-pr-adversarial-code-review-loop.webp&#34;/&gt;&#xA;    &lt;/div&gt;&#xA;    &lt;a href=&#34;https://p.agnihotry.com/images/two-ais-one-pr-adversarial-code-review-loop.webp&#34; itemprop=&#34;contentUrl&#34;&gt;&lt;/a&gt;&#xA;  &lt;/figure&gt;&#xA;&lt;/div&gt;&#xA;&#xA;&lt;p&gt;Plausible diffs are where expensive mistakes hide.&lt;/p&gt;&#xA;&lt;p&gt;Over the last few months, I&amp;rsquo;ve been running a product stack end-to-end myself, with no review queue to hide behind when an AI hand-waves a gnarly edge case. For a while, my workflow was the default one: I&amp;rsquo;d describe a task to Claude, it would write the code, I&amp;rsquo;d skim the diff, and I&amp;rsquo;d merge. It worked. Mostly.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
