Du wirst angemeldet...

Bitte warte, während wir deine Anmeldung überprüfen

Artikel · Samstag, 3. Oktober 2026

Agentic Coding

Top tech stories today across software, hardware, AI, and product launches. Senior engineer audience — skip rumour churn and pre-announcement leaks. Lead with shipping-now stories and what changed for builders.

Von Marius BongartsTech120 Ausgaben
← Zur aktuellen Ausgabe
Ausgaben
5 / 120
Über Nacht von KI aus öffentlichen Quellen erstellt, täglich aktualisiert.
Agentic Coding
Samstag, 3. Oktober 2026
AI Agents - Agentic Coding

Three-layer code review catches what you miss, SonarQube MCP brings static analysis into Claude Code

1 Min. Lesezeit

Three-Layer Code Review

When code generation gets cheap, verification becomes your bottleneck.

A Sonar engineer published his squad's agentic workflow that treats Claude Code like a junior dev—he uses repository-level CLAUDE.md files to mandate verification steps before any task counts as done, including running tests, linters, and SonarQube analysis [Source: Sonar]. The three-layer review—deterministic static analysis, reasoning-based review via Gitar, then human—catches different issue categories before they reach you. His squad now ships four PRs by end of day versus three-to-four days per feature before.

If your review queue is swelling, this pattern might be why.

PRD-Driven Scope Control

Blast radius should decide your prompt size.

The same Sonar workflow calibrates scope based on how much of the codebase a change can touch—high-impact changes get tighter, more precise prompts while low-risk edits run looser [Source: Sonar]. He commits frequently rather than running marathon sessions, keeping context small and fresh. Crucially, he writes his own Jira tickets rather than letting the agent interpret vague requirements—building that mental model himself means better steering later.

Worth adopting if your long sessions keep drifting off-target.

SonarQube MCP Server

Static analysis now lives inside your Claude Code session.

SonarSource released official documentation for connecting their MCP server directly to Claude Code, bringing SonarQube's code quality and security tools into your terminal-based AI workflow [Source: Sonar Docs]. This pairs well with the CLAUDE.md verification patterns from the previous issue—you can now instruct your agent to run SonarQube checks as part of task completion without leaving your session.

One less context switch before you commit.

Quellen
AI Code Review in Agentic Coding Workflows - Sonar
AI Code Review in Agentic Coding Workflows - Sonar
16 hours ago ... Quentin's squad hit that wall directly. The answer is not to lower the bar on what gets merged, it's to make verification automated, multilayered, and fast ...
sonarsource.com
KI-Zusammenfassung

Quentin Chevrin, a front-end developer at Sonar, shares an advanced agentic coding workflow that directly addresses the bottleneck modern teams face: when code generation becomes cheap, verification becomes the constraint. His approach uses repository-level CLAUDE.md files to specify verification steps the agent must complete before tasks are considered done, including running tests, linters, and SonarQube analysis. This multi-layered verification system—combining deterministic SonarQube analysis, reasoning-based review through Gitar, and human review—catches different categories of issues before they reach human reviewers, allowing his squad to open four pull requests by end of day compared to the previous three-to-four days per feature. Quentin's practical PRD-driven workflow treats AI agents like junior developers: he starts with precise prompts, keeps context small by committing frequently rather than running long sessions, and calibrates scope by blast radius depending on codebase impact. He maintains control through active steering rather than parallel sessions, and intentionally writes his own Jira tickets to build the mental model needed to guide the agent effectively. His key constraints include using CLAUDE.md instructions to forbid expensive token operations (like reading full message files) and ensuring the agent never commits code directly—he does that himself to maintain visibility over changes.

Quelle öffnen
Claude Code | SonarQube MCP Server - Sonar Documentation
Claude Code | SonarQube MCP Server - Sonar Documentation
21 hours ago ... For example: "Ping the SonarQube MCP server." Tip: Restart your AI agent for good measure, although it might not be required.
docs.sonarsource.com
Über Nacht zusammengestellt von MorningMail.aiZugestellt um 04:55