#Code Review

Most code review tools show the diff in isolation. With Driver, the agent evaluates changes against the full codebase architecture, established patterns, and conventions.

#Example prompts

• "Review this diff against the codebase architecture"
• "Does this change follow existing patterns in my-backend?"
• "What might this PR break?"
• "Are there any architectural concerns with these changes?"

#What happens

The agent combines multiple Driver tools:

1. get_architecture_overview: Loads the system structure so the agent understands how components relate.
2. get_code_map: Identifies which modules are affected by the change and what depends on them.
3. get_file_documentation: Inspects the specific files being modified to understand existing function signatures, interfaces, and conventions.

The agent then evaluates the diff against this context. It catches issues that a reviewer without full architectural knowledge would miss: broken conventions, unintended coupling, missing error handling in established patterns, and changes that conflict with the system design.