Guides

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_atlas_index - Loads the thematic map so the agent understands which subsystems the change touches.
  2. get_atlas_detail - Opens the sections the change touches, returning their coupling rules and member files so the agent can check the change against the invariants that hold there.
  3. get_code_map - Identifies which modules are affected by the change and what depends on them.
  4. get_related - Returns how each changed file couples to the rest of the codebase: dependency, mirror, and co-change edges. A file that usually moves with one in the diff and is missing from it is worth a question.
  5. change_impact - Sizes the blast radius of a changed symbol and names the tests that reach it, including dependents two or more hops out that a text search does not find.
  6. get_source_file - Reads the specific files being modified to check existing signatures, interfaces, and conventions against the change.

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.

Note: For the best results, paste the diff directly into the conversation or point the agent to the PR. The agent needs both the changes and the codebase context to give a meaningful review.