<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Code-Review on Unbound Force</title><link>https://unboundforce.dev/tags/code-review/</link><description>Recent content in Code-Review on Unbound Force</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright (c) 2025-2026 Unbound Force</copyright><lastBuildDate>Sat, 11 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://unboundforce.dev/tags/code-review/index.xml" rel="self" type="application/rss+xml"/><item><title>Introducing The Curator: Automated Documentation Governance for AI Agent Teams</title><link>https://unboundforce.dev/blog/introducing-the-curator/</link><pubDate>Sat, 11 Apr 2026 00:00:00 +0000</pubDate><guid>https://unboundforce.dev/blog/introducing-the-curator/</guid><description>&lt;h2 id="the-problem--documentation-drift"&gt;The Problem — Documentation Drift&lt;/h2&gt;
&lt;p&gt;Every AI coding agent in a swarm can ship features. They can write code, add tests, refactor internals, and open pull requests. What they do not do — unless someone explicitly tells them to — is check whether the documentation still matches.&lt;/p&gt;</description></item></channel></rss>