<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Review on Vibe Coding</title><link>https://vibecoding.rest/tags/review/</link><description>Recent content in Review on Vibe Coding</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 26 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://vibecoding.rest/tags/review/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub PR Review Skill</title><link>https://vibecoding.rest/skills/gh-address-comments/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/gh-address-comments/</guid><description>&lt;p&gt;This curated Codex skill reads a GitHub pull request&amp;rsquo;s review comments and drives the corresponding fixes back into the branch.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Addressing review feedback is a mechanical loop — read a comment, make the matching change, reply — that&amp;rsquo;s a good fit for automation once the skill knows how to map comments to specific diffs.&lt;/p&gt;</description></item><item><title>How to Review AI-Generated Diffs Without Rubber-Stamping Them</title><link>https://vibecoding.rest/posts/reviewing-ai-generated-diffs/</link><pubDate>Mon, 26 Jan 2026 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/posts/reviewing-ai-generated-diffs/</guid><description>&lt;p&gt;The single most common failure mode in vibecoding isn&amp;rsquo;t a bad prompt — it&amp;rsquo;s a good diff that nobody actually read. Agents are confident, and confident wrong code is easy to approve on autopilot.&lt;/p&gt;</description></item></channel></rss>