Before changing a shared field or interface, use Driver to identify its producers, consumers, and compatibility boundaries. Name the codebases and select the branches you want to assess. Supply the proposed change or diff in the conversation.
- Ask in Driver: “What depends on tenant_id in imports on these branches, and what must change if we rename it to account_id? Cite the producers, consumers, and tests. Return a table with each dependency, required change, compatibility risk, and verification check.”
- Ask Driver to trace references to the field. With prepared Advanced context, ask it to follow relationships and change impact from the defining file or symbol to find dependents.
- Ask it to search literal names in database schemas, configuration, payloads, and generated clients. Add known consumers outside the connected codebases so the plan identifies the teams who must verify them.
- Ask Driver to distinguish changes that can ship together from changes that require a migration, a transitional field, or coordinated deployment. Review that sequence with the responsible engineers.
- Copy the dependency table and migration sequence into the engineering issue. Give each unresolved external consumer an owner before scheduling the contract change.
In an MCP-connected coding assistant, ask the assistant to use get_related and change_impact for the selected file or symbol, then search for literal contracts with grep_source. Advanced is required for the relationship and impact tools; Basic source search can still find explicit references. Check the tool results for the branch being assessed.