Phase 6: Quality Gates & CI/CD for AI Code · 50 min · Claude Code · GitHub Actions · Python

Intent Verification

The diff running without error tells you nothing about whether it did what was actually asked.

Real-world application: Naming the five intent-verification finding categories and applying them to a real, well-documented production incident is direct evidence you think about PR review as a structured discipline, not a vibe check.

What you will learn

Name the five intent-verification finding categories: intent-mismatch, silent-scope, unbacked-claim, doc-drift, missing-impl
Explain what happened in the 2026 Gemini CLI incident and which finding categories it exhibits
Detect a silent-scope violation by comparing a PR's stated scope against its actual diff statistics
Detect an unbacked claim by checking whether a stated claim has corresponding, verifiable evidence in the diff

Introduction

Intent Verification

Objective

Detect silent-scope and unbacked-claim findings by comparing a PR's stated intent against its actual diff statistics, reconstructing the 2026 Gemini CLI incident's numbers.

Unlock the full lesson

You've read the first 2 sections. The rest of this lesson covers The Problem, The Concept, Build, Check Yourself, Key Terms & Next — plus a hands-on lab, quiz, and project artifact.

Create a free account — the opening phases of 29 of 35 courses are free, no credit card.