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.
Build or update the code review knowledge graph. Run this first to initialize, or let hooks keep it updated automatically.
Review the instructions the agent will receive before you install.
Build or incrementally update the knowledge graph for this repository.
list_graph_stats_tool. If last_updated is null, the graph has never been built.full, call build_or_update_graph_tool(full_rebuild=True). Otherwise call build_or_update_graph_tool() for an incremental update.status (ok, partial or error) and summary.code-review-graph install run an update after each edit and before each commit, so manual builds are rarely needed..code-review-graph/graph.db in the repository root..code-review-graphignore are skipped.get_docs_section_tool(section_name="languages").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.
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 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 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.