<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Steve</title>
    <description>The latest articles on DEV Community by Steve (@sonarsteve).</description>
    <link>https://dev.to/sonarsteve</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4064759%2Fc854d683-2fdc-4e07-9eaa-ebe53d931547.jpeg</url>
      <title>DEV Community: Steve</title>
      <link>https://dev.to/sonarsteve</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sonarsteve"/>
    <language>en</language>
    <item>
      <title>How to combine Claude Code review with SonarQube verification</title>
      <dc:creator>Steve</dc:creator>
      <pubDate>Fri, 06 Nov 2026 23:06:19 +0000</pubDate>
      <link>https://dev.to/sonar/how-to-combine-claude-code-review-with-sonarqube-verification-4ib8</link>
      <guid>https://dev.to/sonar/how-to-combine-claude-code-review-with-sonarqube-verification-4ib8</guid>
      <description>&lt;p&gt;A few months ago, a thread in r/ClaudeCode asked a question that I suspect plenty of people have muttered at their terminal: &lt;a href="https://www.reddit.com/r/ClaudeCode/comments/1vtvo0b/" rel="noopener noreferrer"&gt;is /code-review a big waste of tokens?&lt;/a&gt; &lt;strong&gt;&lt;code&gt;/code-review&lt;/code&gt;&lt;/strong&gt; is Claude Code's built-in code review command: it asks Claude to look over your changes for bugs before you merge them.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F8y9nqrhyxcy03sdjmphr.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F8y9nqrhyxcy03sdjmphr.png" alt="Screenshot of a Reddit post in r/ClaudeCode titled &amp;quot;/code-review is a big waste of tokens?&amp;quot;" width="800" height="265"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The original r/ClaudeCode post (&lt;a href="https://www.reddit.com/r/ClaudeCode/comments/1vtvo0b/" rel="noopener noreferrer"&gt;view on Reddit&lt;/a&gt;). User-reported experience, not a Sonar measurement.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The original poster described a routine many developers will recognize: asking Claude to review their pull requests (PRs) in a fresh session. By their estimate, that took 10 to 20 minutes and 5–10% of a session's tokens (the units AI usage is measured and billed in). They then tried the dedicated &lt;code&gt;/code-review&lt;/code&gt; command. About ten minutes in, they noticed it was reviewing a different set of changes than they intended, and they soon reached their session limit. They asked whether the command is only available on Max plans.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;A note on the numbers: everything in this thread is user-reported. I haven't reproduced any of it, and the poster notes their build and unit tests are slow, which may account for some of that time. Review cost depends on your plan, model, effort level, and what you point the review at, so your results will differ.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclosure: I work at Sonar, the company behind SonarQube, so I have a stake in one of the tools mentioned below. Most of this works regardless of which tools you use.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  TLDR
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;/code-review&lt;/code&gt; works on any plan and does find real bugs. What it reports depends on what you point it at and the effort level (how thoroughly it looks) you set, so name the target and pick the level on purpose. A rule-based checker (a tool that checks code against fixed rules) settles the issues a rule can decide, so the review can focus on the rest.&lt;/li&gt;
&lt;li&gt;Split the work. Deterministic checks handle what has a clear yes-or-no answer, like leaked secrets. AI review handles what needs judgment, like whether the change does what the ticket asked.&lt;/li&gt;
&lt;li&gt;Run them in that order: get the deterministic checks passing first, then spend review tokens on what's left.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  AI code review and deterministic analysis: What should each one find?
&lt;/h2&gt;

&lt;p&gt;Review findings come in two broad kinds:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Issues a deterministic check can settle.&lt;/strong&gt; Unchecked user input reaching a database query, hardcoded passwords, risky settings, overly complex functions, missing test coverage. Each has a clear yes-or-no answer.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Issues that need judgment.&lt;/strong&gt; Does the change match the issue or spec? Is that off-by-one really off? What breaks at the edges?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;An AI reviewer can find both, but paying a model to find a hardcoded password is like paying a senior engineer to read every file looking for one: it works, but it's slow and expensive.&lt;/p&gt;

&lt;p&gt;Sonar's &lt;a href="https://www.sonarsource.com/blog/why-fable-5-still-needs-a-second-loop/" rel="noopener noreferrer"&gt;second-loop post&lt;/a&gt; explains why you want both layers: an AI check can answer differently on each run, while a deterministic check gives the same answer every time. Neither replaces the other.&lt;/p&gt;

&lt;p&gt;This &lt;a href="https://www.sonarsource.com/resources/library/multilayered-code-verification-with-gitar-sonarqube-cloud/" rel="noopener noreferrer"&gt;Sonar walkthrough&lt;/a&gt; shows what that looks like in practice. It runs a small demo PR through &lt;strong&gt;Gitar (agentic, AI-driven review)&lt;/strong&gt; and &lt;strong&gt;SonarQube Cloud (deterministic, rule-based analysis)&lt;/strong&gt; as two layers of multilayered verification on the same PR.&lt;/p&gt;

&lt;p&gt;The PR was a Flask API (a small Python web app) with two logic bugs and an untested CSV export endpoint. Between them, the two layers caught every issue below:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Issue in the PR&lt;/th&gt;
&lt;th&gt;Found by&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;A user-supplied filename could write files outside the export folder&lt;/td&gt;
&lt;td&gt;Both layers (SonarQube traced it from the request to the file write, with no AI tokens)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Pagination off by one page&lt;/td&gt;
&lt;td&gt;Agentic review (Gitar)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Sort order reversed compared with the tests&lt;/td&gt;
&lt;td&gt;Agentic review (Gitar)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Exports written to a &lt;code&gt;/tmp&lt;/code&gt; folder any user on the machine can write to&lt;/td&gt;
&lt;td&gt;Deterministic analysis (SonarQube Cloud)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;A web route that doesn't declare which HTTP methods it accepts&lt;/td&gt;
&lt;td&gt;Deterministic analysis (SonarQube Cloud)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The layers also work in sequence. Gitar's fix commit re-triggered CI, and SonarQube rescanned automatically, so the path traversal finding cleared without a manual step. Gitar then fixed everything it had found and approved the PR, and CI (the automated checks that run on every push) went green, but the quality gate, SonarQube's pass/fail bar for new code, still blocked the merge on issues the agentic layer hadn't flagged.&lt;/p&gt;

&lt;p&gt;As the write-up puts it: "Green CI and AI approval does not mean merge-ready!"&lt;/p&gt;

&lt;p&gt;Layered this way, the pair aims to catch as many issues as possible in the most efficient way: fast, deep analysis with high signal and low noise. Deterministic analysis settles the issues that have a clear answer, at no token cost, and agentic review spends tokens on what needs judgment.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;Two caveats:&lt;/em&gt;&lt;/strong&gt; &lt;em&gt;the agentic layer in that demo was Gitar, which Sonar acquired this year, not &lt;code&gt;/code-review&lt;/code&gt;, so what carries over is the method, not the brand. And it's one small PR built for a demo, so read it as what each layer tends to catch, not a catch rate.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  A setup that spends review tokens where they count
&lt;/h2&gt;

&lt;p&gt;Here's what I'd do, cheapest layer first. Steps 1 and 2 work with any deterministic tools, such as linters, type checkers, and security scanners. I'll use SonarQube (Sonar's code verification platform, which runs deterministic analysis; SonarQube Cloud is the cloud-hosted version) for the examples because I work at Sonar and know it best, and it has free options.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Run deterministic analysis while the agent writes
&lt;/h3&gt;

&lt;p&gt;In your editor, &lt;a href="https://www.sonarsource.com/products/sonarqube/ide/" rel="noopener noreferrer"&gt;SonarQube for IDE&lt;/a&gt; is a free extension that flags issues as you type. In a Claude Code session, install the SonarQube plugin from Anthropic's official marketplace and run its setup.&lt;/p&gt;

&lt;p&gt;You'll need Node.js, Docker (or Podman), and a SonarQube account (a free SonarQube Cloud account works, per the &lt;a href="https://github.com/SonarSource/sonarqube-agent-plugins" rel="noopener noreferrer"&gt;setup guide&lt;/a&gt;). Keep Docker running, since the SonarQube MCP Server runs in a container. Run these one at a time, and if Claude Code asks you to run &lt;code&gt;/reload-plugins&lt;/code&gt; after the install, do that first:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;/plugin install sonarqube@claude-plugins-official
/sonarqube:sonar-integrate
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The integrate step installs the SonarQube CLI (a command-line tool), walks you through signing in, and connects Claude Code to your SonarQube account. It also adds hooks that scan your prompts and the files Claude reads for secrets before they reach the model. Prefer the terminal? Install the &lt;a href="https://cli.sonarqube.com/" rel="noopener noreferrer"&gt;SonarQube CLI&lt;/a&gt;, then run &lt;code&gt;sonar auth login&lt;/code&gt; and &lt;code&gt;sonar integrate claude&lt;/code&gt; for the same hooks and MCP server.&lt;/p&gt;

&lt;p&gt;Claude can then fix findings with the exact issue and line in hand, before anyone spends tokens on an open-ended review.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Gate every PR with checks that don't spend tokens
&lt;/h3&gt;

&lt;p&gt;Run your rule-based checks in CI and block merges when they fail; they use no AI tokens.&lt;/p&gt;

&lt;p&gt;SonarQube Cloud is free for up to 5 users and 50,000 lines of private code, including analysis of PRs into your main branch with the default quality gate (its &lt;a href="https://docs.sonarsource.com/sonarqube-cloud/quickstart-guides/quickstart-guide" rel="noopener noreferrer"&gt;quickstart guide&lt;/a&gt; covers CI setup). Public open source projects get a free OSS plan that analyzes every branch and PR. Prefer to host it yourself? SonarQube Community Build is free and open source, but it analyzes your main branch only; PR analysis starts at Developer Edition, which is paid.&lt;/p&gt;

&lt;p&gt;Rule of thumb: don't run &lt;code&gt;/code-review&lt;/code&gt; on a PR until those checks pass. There's no reason to pay a model to rediscover what they already reported.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Run /code-review scoped, sized, and steered
&lt;/h3&gt;

&lt;p&gt;With no target, &lt;code&gt;/code-review&lt;/code&gt; reviews the commits on your current branch that its upstream branch doesn't have yet, plus anything uncommitted. Naming the target makes sure it reviews the changes you meant. It counts toward your plan's usage or API bill, so see &lt;a href="https://code.claude.com/docs/en/costs" rel="noopener noreferrer"&gt;Anthropic's cost docs&lt;/a&gt; for details.&lt;/p&gt;

&lt;p&gt;Name the target every time:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;/code-review 1234&lt;/code&gt; reviews PR #1234&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;/code-review main...my-feature&lt;/code&gt; reviews one branch against another&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;/code-review low 1234&lt;/code&gt; reports only the findings it's most confident in&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Reviewing several PRs? Run one scoped review per PR rather than one sprawling request.&lt;/p&gt;

&lt;p&gt;Pick the effort level on purpose. If you leave it off, &lt;code&gt;/code-review&lt;/code&gt; reuses the last level you typed, even from an earlier session, so after one &lt;code&gt;/code-review max&lt;/code&gt;, a plain &lt;code&gt;/code-review&lt;/code&gt; runs at max too.&lt;/p&gt;

&lt;p&gt;Save &lt;code&gt;/code-review ultra&lt;/code&gt; for changes that warrant it. It's a deeper review that runs several agents in the cloud, so it takes longer than a regular review and is billed differently. It's a research preview, so check &lt;a href="https://code.claude.com/docs/en/ultrareview" rel="noopener noreferrer"&gt;Anthropic's ultrareview docs&lt;/a&gt; for current pricing.&lt;/p&gt;

&lt;p&gt;Then tell the reviewer what not to re-report. &lt;code&gt;/code-review&lt;/code&gt; follows your &lt;code&gt;CLAUDE.md&lt;/code&gt; (the project instructions file Claude Code loads in every session), so a short section steers it. Keep it brief, since every line costs tokens, and adjust the first bullet to match what your checks cover:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight markdown"&gt;&lt;code&gt;&lt;span class="gu"&gt;## Code review&lt;/span&gt;
&lt;span class="p"&gt;
-&lt;/span&gt; Our CI checks (SonarQube) already run deterministic analysis: secrets, injection flaws, risky config, complexity, duplication, test coverage.
&lt;span class="p"&gt;-&lt;/span&gt; Don't re-report anything SonarQube already flags on the PR. Spend findings on what deterministic checks can't judge: does the change match the issue or spec, logic and edge cases, error handling, concurrency, API or contract changes, and whether the tests cover the cases that matter.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  4. For high-risk changes, get a second opinion from a different model
&lt;/h3&gt;

&lt;p&gt;The thread's most upvoted reply hands reviews to a different model (Codex, OpenAI's coding agent) for a second opinion.&lt;/p&gt;

&lt;p&gt;That instinct is right: a model reviewing its own work shares its own blind spots.&lt;/p&gt;

&lt;p&gt;For risky changes, a different model, or a fresh session told to hunt hard for problems, is worth the tokens, though either can still answer differently on another run. So let the rule-based check block the merge, and let a human make the final call.&lt;/p&gt;

&lt;h2&gt;
  
  
  So back to the Reddit thread… is /code-review a &lt;em&gt;“waste of tokens”&lt;/em&gt;?
&lt;/h2&gt;

&lt;p&gt;I think that’s the wrong question to ask about any single reviewer. &lt;code&gt;/code-review&lt;/code&gt; does find real bugs, and it does its best work as one part of your verification setup. A more useful question is whether each kind of check is doing the job it’s best at.&lt;/p&gt;

&lt;p&gt;A rule-based check gives the same answer every time, so it should settle issues like leaked secrets and injection flaws and block the merge when they show up. An AI reviewer brings judgment, so it should focus on intent, logic and edge cases. In the demo PR above, neither one caught everything alone, and together they caught all five issues. If you get the deterministic checks passing first, Claude can spend its whole review on the questions that need judgment.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How are you running reviews in Claude Code?&lt;/strong&gt; I’d love to hear what’s working for you in the comments 👇&lt;/p&gt;

</description>
      <category>ai</category>
      <category>code</category>
      <category>tutorial</category>
      <category>claude</category>
    </item>
    <item>
      <title>Introducing Sonar</title>
      <dc:creator>Steve</dc:creator>
      <pubDate>Wed, 28 Oct 2026 19:00:30 +0000</pubDate>
      <link>https://dev.to/sonar/introducing-sonar-239h</link>
      <guid>https://dev.to/sonar/introducing-sonar-239h</guid>
      <description>&lt;p&gt;If you've worked on a team with a CI pipeline in the last 18 years, there's a good chance SonarQube has failed one of your builds. That part hasn't changed. What has changed is who writes the code. Here's what Sonar looks like when your teammate is an agent.&lt;/p&gt;

&lt;h2&gt;
  
  
  For those about to ship: Sonar's Agent Centric Development Cycle (AC/DC)
&lt;/h2&gt;

&lt;p&gt;Sonar's Agent Centric Development Cycle (AC/DC) is the simplest way to understand what Sonar does in 2026 and where each of our products fits.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://dev.to/dailycontext/code-is-abundant-confidence-is-a-formula-gn6"&gt;Code is becoming more and more abundant&lt;/a&gt; from AI-driven and AI-assisted development and now, software factories.&lt;/p&gt;

&lt;p&gt;The former dev-written 300-line pull request is now an over 1,000-line AI-assisted one. When Sonar surveyed developers, they said 65% of the code they commit is AI-generated or assisted (&lt;a href="https://www.sonarsource.com/resources/state-of-code-developer-survey-2027/" rel="noopener noreferrer"&gt;source&lt;/a&gt;). And PRs written by agents wait 5.3× longer than unassisted ones before a reviewer even picks them up, per &lt;a href="https://linearb.io/resources/software-engineering-benchmarks-report" rel="noopener noreferrer"&gt;LinearB&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The bottleneck is now verification. It usually happens too late: failing tests, rework, and security findings show up after the agent has moved on, and the code that's left behind is the developer's problem. We call this verification debt.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Agent Centric Development Cycle (AC/DC)
&lt;/h2&gt;

&lt;p&gt;Every loop runs the same three stages:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Guide:&lt;/strong&gt; give the agent the right context before it writes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Verify:&lt;/strong&gt; check the output with zero-trust, multilayered verification, never with the model that wrote it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Solve:&lt;/strong&gt; fix what's left, then feed what you learned into the next round.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That loop runs in three places:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Loop&lt;/th&gt;
&lt;th&gt;Where it runs&lt;/th&gt;
&lt;th&gt;When&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;1. Agentic loop&lt;/td&gt;
&lt;td&gt;Inside your coding agent&lt;/td&gt;
&lt;td&gt;While it writes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2. CI verification loop&lt;/td&gt;
&lt;td&gt;At the pull request&lt;/td&gt;
&lt;td&gt;Before merge&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3. Code maintenance loop&lt;/td&gt;
&lt;td&gt;In the background&lt;/td&gt;
&lt;td&gt;On code you've already merged&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Loop 1: Inside your agent
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Sonar Vortex 🌀
&lt;/h3&gt;

&lt;p&gt;Agents don't know your architecture, standards or which packages are safe. Vortex gives context to the agents before they write and checks every file as they write. Customers report up to 92% fewer issues introduced by the agent, and Sonar's benchmarks show up to 36% fewer tokens on navigation-heavy refactoring tasks.&lt;/p&gt;

&lt;p&gt;Also in this loop, and free: SonarQube for IDE flags issues as you (or your agent) type in VS Code, Cursor, JetBrains, and other IDEs. The SonarQube MCP Server and SonarQube CLI let agents like Claude Code, Cursor, and Codex call SonarQube analysis directly.&lt;/p&gt;

&lt;h2&gt;
  
  
  Loop 2: At the pull request
&lt;/h2&gt;

&lt;h3&gt;
  
  
  SonarQube - Deterministic quality gates ⛩️
&lt;/h3&gt;

&lt;p&gt;What Sonar is known for. The deterministic quality gate for every change, across 45+ languages and frameworks. It runs as SonarQube Cloud or SonarQube Server.&lt;/p&gt;

&lt;h3&gt;
  
  
  SonarQube Advanced Security 🔐
&lt;/h3&gt;

&lt;p&gt;Checks every installed open-source package for vulnerabilities, malware and license risk, and follows untrusted data into your dependencies. Reachability shows which vulnerabilities your code actually calls, so you can fix those first.&lt;/p&gt;

&lt;p&gt;It's an add-on product that extends SonarQube's core security  capabilities (SAST, taint analysis, secrets detection, IaC scanning) with Advanced SAST and Software Composition Analysis (SCA).&lt;/p&gt;

&lt;h3&gt;
  
  
  Gitar - The code verification agent 🔎
&lt;/h3&gt;

&lt;p&gt;Gitar reviews every PR with the context of your codebase and your team's conventions, and it's tuned for signal: one consolidated comment, with inline notes only where they matter. Because it reads what a change is trying to do, it catches the logic and behavior bugs that deterministic rules aren't built for. SonarQube covers the known issues; Gitar covers intent. Together they form multilayered verification: deterministic analysis for known issues, agentic review for intent, and neither trusts the agent to check its own work.&lt;/p&gt;

&lt;p&gt;When CI breaks, Gitar reads your pipeline, separates real breakage from flaky tests and infrastructure noise, and finds the root cause. Then it commits a fix to the branch, within the rules you define, and keeps going until CI is green. You write those rules in plain English, and they live in your repo next to your code. It works with GitHub, GitLab, Bitbucket, and Azure DevOps, and with the CI you already run: GitHub Actions, GitLab Pipelines, CircleCI, Buildkite, Jenkins, and more.&lt;/p&gt;

&lt;h2&gt;
  
  
  Loop 3: In the background
&lt;/h2&gt;

&lt;h3&gt;
  
  
  SonarQube Hunter Agent 🏹
&lt;/h3&gt;

&lt;p&gt;Hunter Agent is an AI security agent built for this class of flaw: broken access control (like IDOR), business logic abuse (skipped workflow steps, missing rate limits), and authentication and session gaps. It works like a security researcher, running Sonar's security playbooks across your whole codebase and following data and identity flows between files. It confirms every lead before reporting it, which gets it to 90% precision. And it's repeatable: scan twice, get the same results.&lt;/p&gt;

&lt;p&gt;Confirmed findings land in your SonarQube issues with a severity, a plain explanation, and the exact line, ready to assign and fix. So far it has uncovered 200+ zero-day vulnerabilities in open-source applications.&lt;/p&gt;

&lt;h3&gt;
  
  
  SonarQube Remediation Agent 🛠️
&lt;/h3&gt;

&lt;p&gt;Every codebase has a backlog of known issues nobody gets to. The Remediation Agent works through it. Pick issues in SonarQube by severity, or project and send issues in batches, or put it on a daily or weekly schedule. It also picks up PRs that failed their quality gate.&lt;/p&gt;

&lt;p&gt;For each fix, it applies the change in a sandbox and re-runs Sonar's analysis, the same engine that raised the issue. If the issue isn't gone, or a new one shows up, the fix is thrown away. Only fixes that pass your quality gate become pull requests, grouped by rule and file type so one review covers a batch. It never merges: your branch protection and reviewers apply as usual.&lt;/p&gt;

&lt;h2&gt;
  
  
  Tutorial: Get riffing with Gitar 🎸
&lt;/h2&gt;

&lt;p&gt;If you want to see one of these loops running today, I'd start with Gitar. There's a free 14-day trial, and it doesn't require a credit card.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Step-by-step using GitHub&lt;/strong&gt;&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Sign in at &lt;a href="https://app.gitar.ai" rel="noopener noreferrer"&gt;app.gitar.ai&lt;/a&gt; using GitHub.&lt;/li&gt;
&lt;li&gt;Connect your code. On GitHub you install the Gitar app, then choose all your repos or just a few. GitLab's a bit different. There, you make a personal access token for a dedicated user (a service account works too) and paste that into the Gitar dashboard.&lt;/li&gt;
&lt;li&gt;Now open a PR. Already have a few open? Gitar can run on those, straight from the dashboard.&lt;/li&gt;
&lt;li&gt;Wait a couple of minutes. gitar-bot 🤖 leaves a summary comment on the PR, plus inline comments where it found something.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;See something in there you want fixed? Tell it. A plain reply on the comment is enough, and Gitar comes back with a new commit. Want it to apply fixes without asking? Post this as a comment on the PR:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;gitar auto-apply:on
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;On Bitbucket or Azure DevOps? Setup for both is in the &lt;a href="https://docs.gitar.ai/quickstart" rel="noopener noreferrer"&gt;Gitar docs&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  TL;DR
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;AI agents write code fast, verifying and shipping that code is the bottleneck.&lt;/li&gt;
&lt;li&gt;Sonar runs one loop (Guide, Verify, Solve) in three places: in your agent, at the pull request, and in the background.&lt;/li&gt;
&lt;li&gt;Each product has a home in one of those places, and SonarQube's analysis runs under all three.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Want more? Check out our &lt;a href="https://www.sonarsource.com/developers/blueprints/" rel="noopener noreferrer"&gt;Developer Guides&lt;/a&gt; or our blueprints on &lt;a href="http://github.com/sonar-samples" rel="noopener noreferrer"&gt;github.com/sonar-samples&lt;/a&gt; and get started.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>security</category>
      <category>code</category>
      <category>beginners</category>
    </item>
  </channel>
</rss>
