<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Review-Pr on Unbound Force</title><link>https://unboundforce.dev/tags/review-pr/</link><description>Recent content in Review-Pr on Unbound Force</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright (c) 2025-2026 Unbound Force</copyright><lastBuildDate>Sun, 23 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://unboundforce.dev/tags/review-pr/index.xml" rel="self" type="application/rss+xml"/><item><title>Your CI Failed — But Was It Your Fault? How /review-pr Separates Signal from Noise</title><link>https://unboundforce.dev/blog/ci-failure-classification/</link><pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate><guid>https://unboundforce.dev/blog/ci-failure-classification/</guid><description>&lt;h2 id="the-red-x-that-wastes-your-morning"&gt;The Red X That Wastes Your Morning&lt;/h2&gt;
&lt;p&gt;You open your pull request. CI is red. Your stomach drops — and then you spend the next hour discovering that the failure has nothing to do with your changes. A flaky integration test that fails one run in ten. A lint violation introduced three PRs ago. A dependency warning that nobody addressed last sprint. You didn&amp;rsquo;t break anything, but you&amp;rsquo;re the one staring at log output trying to prove it.&lt;/p&gt;</description></item></channel></rss>