<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Clawpatch - Tag - 508.dev Blog</title><link>http://blog.508.dev/tags/clawpatch/</link><description>508.dev Blog</description><generator>Hugo 0.146.0 &amp; FixIt v0.3.20</generator><language>en</language><managingEditor>caleb@508.dev (508.dev LLC)</managingEditor><webMaster>caleb@508.dev (508.dev LLC)</webMaster><lastBuildDate>Fri, 12 Jun 2026 11:43:00 +0200</lastBuildDate><atom:link href="http://blog.508.dev/tags/clawpatch/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Use clawpatch to Fix Your Vibecoded AI Slop</title><link>http://blog.508.dev/posts/how-to-use-clawpatch-to-fix-your-vibecoded-ai-slop/</link><pubDate>Fri, 12 Jun 2026 11:43:00 +0200</pubDate><guid>http://blog.508.dev/posts/how-to-use-clawpatch-to-fix-your-vibecoded-ai-slop/</guid><category domain="http://blog.508.dev/categories/technical/">Technical</category><category domain="http://blog.508.dev/categories/programming/">Programming</category><description>I vibecoded something useful, then had to deal with the usual mess that comes after. This is a short guide to using clawpatch to review the repo, fix one thing at a time, and slowly make the codebase a bit less cursed.</description></item></channel></rss>