Review code changes against the previous commit and identify affected files and functions. Use dependency relationships to assess risk, check missing tests, and produce a focused report with issues and recommendations.
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
Review the instructions the agent will receive before you install.
Review only the changed code and its blast radius.
get_minimal_context_tool(task="review changes"). If it returns status: not_ready, call build_or_update_graph_tool() and continue.detect_changes_tool(detail_level="minimal") for risk-scored changed functions, test gaps and affected flows. Changes come from git diff against HEAD~1; if the argument names a file, pass it in changed_files.get_review_context_tool(detail_level="minimal") when you need source snippets for the changed areas and review_guidance (untested functions, wide blast radius, inheritance changes).query_graph_tool(pattern="tests_for", target="<function>").detail_level="standard" only for a high-risk item the minimal output leaves unclear. Do not load whole files unless a snippet is not enough.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Build or refresh a knowledge graph, a map of code relationships used for code review. Choose a full rebuild or an incremental update, then report the operation's status and summary.
Investigate bugs using a graph of code relationships. Find relevant functions, trace calls and execution paths, check recent changes, and assess what a proposed fix could affect before reading and changing the implementation.
Explore an unfamiliar codebase using a graph of code relationships. Inspect its structure, find functions and classes, trace calls and imports, follow execution paths, and locate large functions for closer investigation.
Plan refactoring with dependency analysis, which shows how code parts rely on each other. Find candidates and unreferenced code, preview and apply renames, and compare the resulting impact with the original plan.
Review code changes using a knowledge graph, a map of code relationships, to assess risk and affected behavior. Organize findings by severity, identify missing tests, suggest fixes, and provide a merge recommendation.
Review all changes in a pull request or branch against its base branch. Use a knowledge graph, a map of code relationships, to report affected files and functions, test coverage, API compatibility issues, and recommended actions.