Skip to main content

Code Review

Scenario: You are reviewing a pull request and need full project context to evaluate the changes.

The Problem​

Code reviews often lack context. You see the diff but not the bigger picture — which other code depends on the changed function, what the documentation says about the expected behavior, or whether there was a past decision about this component.

The Workflow​

When reviewing changes to a function, find all related code:

code_docs_search({ query: "validateUserToken" })
code_get_symbol({ nodeId: "src/auth/token.ts::validateUserToken" })

See the full definition, including the function body, to understand what it does today.

2. Check Cross-References​

Bridge the gap between code and documentation:

docs_cross_references({ symbol: "validateUserToken" })

This returns the code definition, any documentation examples that mention the symbol, and surrounding explanations. If the docs describe a contract that the PR violates, you will see it here.

Check if there are notes about design decisions related to the changed code:

notes_docs_search({ query: "token validation" })
notes_docs_search({ query: "authentication" })

Past decisions often explain constraints that are not obvious from the code alone.

4. Find Linked Tasks​

See if there are tasks connected to the modified code:

tasks_find_linked({ targetId: "src/auth/token.ts", targetGraph: "code" })

This reveals whether the change is part of a tracked effort, or whether it touches code with open issues.

5. Search Documentation​

Check what the docs say about the feature area:

docs_search({ query: "token validation flow" })
docs_search({ query: "authentication error handling" })

6. Explore Examples​

Find code examples in the documentation that demonstrate the expected usage:

docs_find_examples({ symbol: "validateUserToken" })
docs_explain_symbol({ symbol: "validateUserToken" })

If the PR changes the function signature, examples may need updating too.

Key Tools​

ToolPurpose in code review
code_searchFind code related to the PR changes
code_get_symbolRead the full source of a specific symbol
docs_cross_referencesGet code + docs + explanations in one call
notes_searchFind past decisions about the changed area
tasks_find_linkedSee tasks connected to the modified files
docs_searchFind relevant documentation sections
docs_find_examplesFind doc code examples using the changed symbols

Tips​

  • Start with docs_cross_references to get the full picture before diving into specifics.
  • Check notes_search for architecture decisions — they often explain non-obvious constraints.
  • Use tasks_find_linked to see if the change relates to tracked work items or known issues.