Database migration review
Design an agent that reviews every database migration before it ships: locking behavior, backfill cost, rollback safety. What does it need to know about production — not just the DDL — to judge whether a migration is dangerous, and what may it do with that judgment: comment, block the merge, or something else? How would you build confidence in its calls using your migration history, and how do you pitch it after the last bad migration took the site down?
review_migration_risk(operations: list[str], row_counts: list[int]) → list[str][["add_column_nullable","create_index","drop_column"],[50000000,50000000,50000000]]out["safe","ack_required","ack_required"][["create_index","create_index"],[9999,10000]]out["safe","warn"][["alter_column_type"],[-1]]out["ack_required"]Turn the fuzzy goal into a bounded agent task. Say what the agent reads, what it may do on its own versus draft for a human, and what it must never touch. Then earn the trust: how you’d verify it before rollout, and the pitch (the problem, what you built, why it matters).
Agent build: design the agent in plain language (or narrate it). The coach grades the decomposition, the guardrails, the verification plan, and the pitch.