Question
You generate user-facing release notes with an AI from a batch of merged PRs. One line reads: 'Added dark mode support across the dashboard.' Looking at the PRs, dark mode was only added to the settings page, and one PR that was reverted before release still shows up as a shipped feature. How do you verify AI-generated release notes describe what actually shipped, not just what the PRs talked about?
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.