Review a PR or branch diff using the knowledge graph for full structural context. Outputs a structured review with blast-radius analysis.

Review PR Perform a comprehensive code review of a pull request or branch diff using the knowledge graph. Token optimization: Before starting, call get docs section tool(section name="review pr") for the optimized workflow. Never include full files unless explicitly asked. Steps 1. Identify the changes for the PR: If a PR number or branch is provided, use git diff main...<branch to get changed files Otherwise auto detect from the current branch vs main/master 2. Update the graph by calling build or update graph tool(base="main") to ensure the graph reflects the current state. 3. Get the full review context by calling get review context tool(base="main") : This uses main (or the specified base branch) as the diff base Returns all changed files across all commits in the PR 4. Analyze impact by calling get impact radius tool(base="main") : Review the blast radius across the entire PR Identify high risk areas (widely depended upon code) 5. Deep dive each changed file : Read the full source of files with significant changes Use query graph tool(pattern="callers of", target=<func ) for high risk functions Use query graph tool(pattern="tests for", target=<func ) to verify test coverage Check for breaking changes in public APIs 6. Generate structured review output : Tips For large PRs, focus on the highest impact files first (most dependents) Use semantic search nodes tool to find related code the PR might have missed Check if renamed/moved functions have updated all callers

review-pr