<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Graph on cloud_affects</title><link>https://cloudaffects.com/tags/graph/</link><description>Recent content in Graph on cloud_affects</description><generator>Hugo</generator><language>en</language><copyright>CC BY-NC-SA 4.0</copyright><lastBuildDate>Wed, 08 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://cloudaffects.com/tags/graph/index.xml" rel="self" type="application/rss+xml"/><item><title>code-review-graph — Static Analysis via Dependency Graph</title><link>https://cloudaffects.com/gems/code-review-graph/</link><pubDate>Wed, 08 Apr 2026 00:00:00 +0000</pubDate><guid>https://cloudaffects.com/gems/code-review-graph/</guid><description>&lt;figure&gt;
 &lt;picture&gt;
 &lt;source srcset="https://cloudaffects.com/gems/code-review-graph/diagram1_before_vs_after_hu_c30cefca911662c2.webp" type="image/webp"&gt;
 &lt;img src="https://cloudaffects.com/gems/code-review-graph/diagram1_before_vs_after.png" alt="Before vs after code review graph" loading="lazy" /&gt;
 &lt;/picture&gt;
 
 &lt;/figure&gt;


&lt;p&gt;&lt;a href="https://github.com/tirth8205/code-review-graph"&gt;code-review-graph&lt;/a&gt; builds a directed graph of your codebase and uses it to run code review. Functions, calls, imports, tests, all connected. When a file changes, the tool traces dependents before touching review logic. Blast radius first.&lt;/p&gt;
&lt;p&gt;The storage choice is the part I&amp;rsquo;d steal first: one SQLite file in WAL mode, holding the graph, metadata, and vector embeddings as binary blobs. No Chroma, no Qdrant, no separate process to keep alive. Incremental updates via SHA-256 mean unchanged files get skipped entirely. On a 2,900-file repo, a full re-traversal runs in under 2 seconds.&lt;/p&gt;</description></item></channel></rss>