Question
Your team uses an AI to auto-generate PR descriptions from the diff. On a PR that refactors a caching layer, the generated summary says 'This change improves cache hit rates by ~30% and fixes a memory leak.' Your actual diff just renames variables and extracts a helper — no benchmark, no leak fix. How do you handle AI-generated PR summaries so they help reviewers instead of misleading them?
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.