Question
Six months into heavy agent use, your TypeScript monorepo has quietly fractured: there are four ways to fetch data, three date-handling utilities, two competing validation approaches, and a sprawl of one-off helper functions agents generated instead of reusing existing ones. No single PR was wrong; the drift is emergent. As the staff engineer, how do you diagnose the damage, decide what's worth consolidating, and stop agents from re-introducing the same divergence next quarter — without a heavy-handed freeze?
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.