Pull requests move faster than review capacity can match. Teams write code at agent speed, but build checks and reviewer bandwidth have not kept pace, so every red build still needs someone to open the log, and every PR still waits on a human read.

In this session, a Sonar developer content engineer walks through Gitar, Sonar's AI code verification agent, on a real pull request. Watch Gitar flag a bug that passes every test, diagnose a CI failure caused by a time zone mismatch between Postgres and Python, and push verified fixes directly to the branch, all without a reviewer leaving the PR.

You will see:

• How Gitar reads a PR description and the surrounding code to check whether a change does what it claims to do
• How Gitar reads CI logs to separate real failures from flaky tests, then explains the root cause
• How a two-word reply, "Gitar fix," pushes a commit that reruns CI and resolves the finding
• How Gitar and SonarQube work as complementary layers, with SonarQube applying deterministic static analysis and Gitar evaluating intent
• How the insights dashboard tracks findings, fixes, and recurring CI failure patterns across every repository

This session covers the fundamentals: installing Gitar on a GitHub organization, understanding the automation toggles for merge blocking, approvals, and reruns, and setting expectations for what a first week with Gitar looks like.