Domain rename across polyglot codebase
You need to rename a core domain concept across a polyglot repo — the term `tenant` becomes `organization` everywhere: class names, DB columns, API field names, config keys, comments, and a public webhook payload field. A teammate suggests letting the AI agent do a repo-wide text replace. What goes wrong with that approach, and how do you actually scope and verify this rename?
Implement
classify_rename_occurrences(occurrences: list[str], old_term: str) → list[str]Examples
in
[["code|TenantService","db|tenant_id","code|multitenant"],"tenant"]out["rename","migrate","skip"]in
[["webhook|tenantId","comment|tenancy","config|tenant_mode"],"tenant"]out["migrate","skip","rename"]in
[[],"tenant"]out[]What a strong answer looks like
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.
0:00 of about 16 min
Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.