REPOSITORY EXPLORER

The product spans 4 repos

crossreview understands the dependency edges between them. A change in one is reviewed against the code in the others.

shared-models

data field source of truth

Customer, Order, Invoice

customer-api

producer

GET /v1/customers/:id → Customer

shared-models

billing-service

consumer

reads Customer.email for invoices

shared-models

frontend-app

consumer

renders Customer.displayName + email

customer-api

THE COUPLING crossreview EXPLOITS

Customer in shared-models is the load-bearing contract. Its email field is read by billing-service; its displayName is rendered by frontend-app. Rename either and the diff looks clean — but two other repos break. That is exactly the class of bug crossreview is built to catch.