▶ Watch ↗38:07
Conference affiliation: Sonar
Authored by Taylor Luttrell-Williams, identified as a developer content engineer at Sonar, and published April 27, 2026. The guide connects Gemini Code Assist to SonarQube through MCP and uses project instructions to make generation, analysis, issue retrieval, repair, and re-analysis part of one workflow. A Flask example fails its quality gate because of insufficient test coverage; after adding tests, the agent separately checks for remaining open issues rather than equating a passing gate with zero findings.
sonarsource.comAuthored by Luttrell-Williams and published May 7, 2026. Explains how generated code can compile and pass tests while introducing dependencies that violate architectural boundaries. Distinguishes the current architecture recovered from source, an intended architecture expressed as permitted dependencies, context supplied to an agent before generation, and subsequent analysis that detects deviations. This establishes his authorship of the explanation, not creation of SonarQube architecture management.
sonarsource.comAuthored by Luttrell-Williams and published June 14, 2026. Walks through GitHub App installation, repository selection, initial scanning, pull-request summaries and inline feedback, and requesting fixes through review comments. Describes follow-up fixes arriving as new commits rather than force pushes. His documented contribution is the onboarding guide, not authorship or ownership of Gitar.
sonarsource.comAuthored by Luttrell-Williams and published July 20, 2026. Documents installation, keychain-backed authentication through the SonarQube CLI, and an analyze-before-commit workflow inside Kiro. Explains that analysis uses complete file content for accuracy while a snippet filter limits reported findings to newly generated code; remediation is followed by another analysis.
sonarsource.comAuthored by Luttrell-Williams and published August 17, 2026. Explains how credentials can enter model requests through deliberately pasted prompts or routine context gathering, including reads of environment files. Advocates dedicated local secrets scanning independent of model judgment, blocking sensitive prompts or file reads before transmission, with additional protection in the IDE and pull-request workflow.
sonarsource.comAuthored by Luttrell-Williams and published September 21, 2026. Covers a dedicated service account, token scopes, project service hooks, pull-request review, CI failure analysis, and automatic fix commits without modifying pipeline definitions. Its TypeScript example returns a string despite declaring a number return type; review additionally identifies missing validation and maintainability improvements. The guide explicitly sequences repair as a fix commit followed by an Azure Pipelines rerun, with further repair attempts possible if that rerun fails.
sonarsource.comAuthored by Luttrell-Williams, identified as a developer content engineer, and published October 28, 2026. Documents assigning Hunter Agent findings to Remediation Agent, sandboxed patch generation and quality-gate validation, and human review of resulting pull requests. A privilege-escalation example restricts editable profile fields to username and email and makes promotion administrator-only. The guide highlights silently ignored profile updates, changed client behavior, and missing automated tests despite a passing gate. The agent opens pull requests but never merges them.
sonarsource.comTaylor Luttrell-Williams is a developer content engineer at Sonar who writes practical guides and technical essays on code quality, security, and AI-assisted development. His work explains how developers can connect coding agents to independent analysis, act on the findings, and review automated repairs. He pays particular attention to what a successful check leaves unanswered: code can pass tests while violating architectural decisions, and a security fix can pass automated analysis while changing behavior that users depend on.
Luttrell-Williams’s April 2026 Gemini Code Assist guide makes verification part of the coding task itself. It connects the agent to SonarQube through the Model Context Protocol (MCP), which lets agents call external tools. Project instructions tell the agent to generate code, run analysis, retrieve findings, make repairs, and scan again before declaring the task complete.
The guide follows a small Flask application through a failed quality gate—a set of acceptance thresholds—and an attempt to improve its test coverage. Luttrell-Williams distinguishes passing that gate from resolving every detected issue: findings below the blocking threshold can remain. His workflow therefore includes a separate check for open issues after the gate passes.
His July 2026 Kiro integration guide applies analysis before commit. It explains why the analyzer needs the complete file even when the developer wants feedback only on newly generated code: full-file context supports the analysis, while filtering the reported findings keeps the review focused on the current change.
Luttrell-Williams also writes about automated review beyond the editor. His Gitar onboarding guide for GitHub walks developers from repository connection to pull-request feedback and fixes requested through comments. His September 2026 Azure DevOps guide separates code-review findings from continuous-integration (CI) failure analysis. In its example, a TypeScript function promises a number but returns a string; the build diagnosis explains that failure, while the review also identifies missing input validation and other improvements. He makes the repair sequence explicit: Gitar pushes a fix commit, Azure Pipelines reruns against it, and another failure may require another attempt.
Across his essays and guides, Luttrell-Williams develops several practical distinctions:
▶ Watch ↗38:07
▶ Watch ↗14:09
Loading more talks and highlights…