<?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 Vibe Coding</title><link>https://vibecoding.rest/category/code-review/</link><description>Recent content in Code Review on Vibe Coding</description><generator>Hugo</generator><language>en</language><atom:link href="https://vibecoding.rest/category/code-review/index.xml" rel="self" type="application/rss+xml"/><item><title>Qodo</title><link>https://vibecoding.rest/tools/qodo/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/tools/qodo/</guid><description>&lt;p&gt;Qodo focuses on what happens before and around a merge rather than writing the code itself: a multi-agent review system analyzes pull requests for bugs and standards violations, paired with Qodo Cover for generating unit tests against existing code.&lt;/p&gt;</description></item><item><title>CodeRabbit</title><link>https://vibecoding.rest/tools/coderabbit/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/tools/coderabbit/</guid><description>&lt;p&gt;CodeRabbit reviews every pull request automatically, posting a summary of the change plus inline comments on specific lines, aimed at being the fastest AI reviewer to set up and the least noisy in what it flags.&lt;/p&gt;</description></item><item><title>Greptile</title><link>https://vibecoding.rest/tools/greptile/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/tools/greptile/</guid><description>&lt;p&gt;Greptile reviews pull requests with context pulled from the entire indexed codebase rather than just the diff itself, aiming to catch bugs that only show up when you know how a changed function is actually called elsewhere.&lt;/p&gt;</description></item><item><title>Codacy</title><link>https://vibecoding.rest/tools/codacy/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/tools/codacy/</guid><description>&lt;p&gt;Codacy runs static analysis, security scanning, and coverage checks on every commit and pull request, surfacing issues as a quality score and letting teams enforce consistent standards across large codebases.&lt;/p&gt;</description></item><item><title>DeepSource</title><link>https://vibecoding.rest/tools/deepsource/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/tools/deepsource/</guid><description>&lt;p&gt;DeepSource continuously analyzes repositories for bugs, security vulnerabilities, performance issues, and anti-patterns, and can generate automated fix-it patches that developers review and merge directly.&lt;/p&gt;&#10;&lt;h2 id="why-it-stands-out"&gt;Why it stands out&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Autofix patches&lt;/strong&gt; — many detected issues come with a ready-to-merge fix rather than just a flagged line.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Low false-positive focus&lt;/strong&gt; — rules are curated to avoid the noisy, low-value warnings common in generic linters.&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Works alongside CI&lt;/strong&gt; — runs as a check on every commit and PR without requiring teams to rewrite existing pipelines.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="good-for"&gt;Good for&lt;/h2&gt;&#10;&lt;p&gt;Teams that want continuous static analysis with actionable, auto-generated fixes rather than just a list of warnings.&lt;/p&gt;</description></item><item><title>CodeScene</title><link>https://vibecoding.rest/tools/codescene/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/tools/codescene/</guid><description>&lt;p&gt;CodeScene analyzes both code structure and version-control history to identify hotspots, code health decline, and knowledge risk (bus factor), and includes automated PR review that flags maintainability regressions in new and AI-generated code.&lt;/p&gt;</description></item><item><title>Bito</title><link>https://vibecoding.rest/tools/bito/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/tools/bito/</guid><description>&lt;p&gt;Bito is an AI coding assistant that pairs an IDE/CLI chat companion with an automated code review agent (AI Code Review Agent) that comments on pull requests, checking for bugs, security issues, and code standard violations.&lt;/p&gt;</description></item><item><title>What The Diff</title><link>https://vibecoding.rest/tools/what-the-diff/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/tools/what-the-diff/</guid><description>&lt;p&gt;What The Diff installs as a GitHub app and posts an AI-generated plain-language summary of what changed in each pull request, aimed at making diffs faster to understand for reviewers and teammates outside the immediate context.&lt;/p&gt;</description></item><item><title>Sourcery</title><link>https://vibecoding.rest/tools/sourcery/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/tools/sourcery/</guid><description>&lt;p&gt;Sourcery started as a Python refactoring tool built into the IDE and has expanded into automated pull request review, suggesting concrete code improvements for readability, performance, and adherence to best practices.&lt;/p&gt;</description></item><item><title>Ellipsis</title><link>https://vibecoding.rest/tools/ellipsis/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/tools/ellipsis/</guid><description>&lt;p&gt;Ellipsis reviews pull requests automatically, leaving comments on bugs and style issues, and can go a step further by opening follow-up commits that fix the problems it finds rather than just describing them.&lt;/p&gt;</description></item><item><title>Graphite</title><link>https://vibecoding.rest/tools/graphite/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/tools/graphite/</guid><description>&lt;p&gt;Graphite is a code review and PR workflow tool built around stacked diffs, helping teams break large changes into small, dependent pull requests, and pairs that workflow with Graphite&amp;rsquo;s own AI reviewer (Diamond) that comments automatically on new PRs.&lt;/p&gt;</description></item><item><title>Reviewpad</title><link>https://vibecoding.rest/tools/reviewpad/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/tools/reviewpad/</guid><description>&lt;p&gt;Reviewpad lets teams define pull request automation as code, covering reviewer assignment, labeling, and merge rules, and layers AI-generated review comments on top so common issues get flagged without manual triage.&lt;/p&gt;</description></item><item><title>Codeflash</title><link>https://vibecoding.rest/tools/codeflash/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/tools/codeflash/</guid><description>&lt;p&gt;Codeflash analyzes Python functions, generates candidate optimizations, and verifies each one for correctness and measured speedup before opening a pull request, focusing specifically on runtime performance rather than general style or bugs.&lt;/p&gt;</description></item><item><title>Sonar</title><link>https://vibecoding.rest/tools/sonar/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/tools/sonar/</guid><description>&lt;p&gt;Sonar has scanned code for bugs, vulnerabilities, and code smells since SonarQube&amp;rsquo;s early days, and now extends that static analysis foundation with AI Code Assurance and AI-powered review features that specifically check AI-generated code against the same quality gates used for human-written code.&lt;/p&gt;</description></item></channel></rss>