<?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 Unbound Force</title><link>https://unboundforce.dev/tags/review/</link><description>Recent content in Review on Unbound Force</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright (c) 2025-2026 Unbound Force</copyright><lastBuildDate>Sun, 03 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://unboundforce.dev/tags/review/index.xml" rel="self" type="application/rss+xml"/><item><title>Your CI Failed — But Was It Your Fault? How /uf.review-pr Separates Signal from Noise</title><link>https://unboundforce.dev/blog/review-pr-causality/</link><pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate><guid>https://unboundforce.dev/blog/review-pr-causality/</guid><description>&lt;h2 id="the-problem"&gt;The Problem&lt;/h2&gt;
&lt;p&gt;You open a pull request. CI runs. Two checks fail. You spend 30 minutes investigating, only to discover that both failures predate your changes — a flaky integration test and a lint rule that was added to the base branch after you created your feature branch.&lt;/p&gt;</description></item></channel></rss>