Question
Overnight, an AI agent landed a stack of 6 commits in your Go monorepo (renamed a package, extracted an interface, updated ~40 call sites, bumped a dep, reformatted, added a feature). This morning one flaky-looking integration test, `TestPaymentRetry_HonorsBackoff`, fails ~30% of the time on CI but passed in every commit's own check. You suspect one of the agent's changes introduced it. How do you isolate which change is responsible without just eyeballing 6 commits?
Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it — tests, edge cases, reading critically — and how you’d re-prompt or decompose to get it right.
Vibe coding: describe the solution in plain language (or narrate it) and the coach grades your approach. Generating runnable code from your description is coming next.