Review

It walks you through analyzing a codebase by mapping integrations, measuring coupling strength and distance, factoring in domain volatility, then flagging the imbalances that actually matter. The interaction design is careful: it reads your code and docs first, shows you what it learned before asking clarifying questions, and only asks things that would change the assessment. It's opinionated about not flagging everything, which is good because most review tools drown you in noise. Best used when you suspect architectural problems but can't articulate why changes feel expensive, or when you need to explain coupling issues to a team in terms they can act on.