Explore relationships between functions and files using a prebuilt code graph, a map of code dependencies. Trace bugs, inspect callers and execution paths, and assess the impact of refactoring or proposed changes.
Query the pre-built code-review-graph knowledge graph (Tree-sitter, whole monorepo) instead of walking call chains with Grep+Read – 2-6x cheaper, and it catches dynamic dispatch that grep misses. Use for ANY task that spans multiple files, even when the user never mentions a graph or asks for it - fixing or tracing a bug ("fix this bug", "why does X happen", "trace this"), exploring unfamiliar code ("how does X work", "who calls X", "what imports Y", "where is X used or handled"), planning or doing a refactor ("rename X", "is it safe to change or remove X", "what would break", "blast radius", "find dead code"), or reviewing changes ("review this PR", "review this branch or diff"). When you are about to Grep for a symbol's callers, callees, or importers, use this skill.
Review the instructions the agent will receive before you install.
Four modes (explore, debug, refactor, review) share the same setup and tools. Full setup, version pin, rebuild, troubleshooting: .ai/MCP.md ("code-review-graph MCP").
Graph MCP tools are deferred, so a direct call fails with InputValidationError. Load schemas first with one ToolSearch (comma-separate the tools the task needs):
ToolSearch query: "select:mcp__code-review-graph__query_graph_tool,mcp__code-review-graph__get_impact_radius_tool,mcp__code-review-graph__detect_changes_tool,mcp__code-review-graph__get_affected_flows_tool"
A graph built on another branch makes detect_changes report function names from unrelated files. The PostToolUse hook syncs after edits; rebuild manually after git checkout / git pull / large merges:
pipx run code-review-graph==2.3.6 status
pipx run code-review-graph==2.3.6 build
list_graph_stats, then list_communities and get_community.semantic_search_nodes finds a function or class by name (keyword match).query_graph with callers_of / callees_of / importers_of / children_of.list_flows and get_flow for execution paths.semantic_search_nodes for code related to the symptom.query_graph callers_of and callees_of; the triggering entry point is usually upstream.get_flow through suspect areas; get_impact_radius on suspect files.detect_changes (recent changes are the most common cause).get_impact_radius and get_affected_flows before touching code.refactor_tool mode rename previews every affected location; dead_code finds unreferenced code; suggest proposes community-driven splits.apply_refactor_tool with the refactor_id applies a previewed rename.detect_changes afterwards.refactor_tool, apply_refactor_tool, and find_large_functions are not validated on this codebase: treat output as hypotheses, verify each edit against the code, and preview before applying.
detect_changes (risk-scored), get_affected_flows, get_impact_radius.*.spec.js / *.unit.js (tests_for returns 0 incorrectly for many files). Suggest cases for untested changes.Report grouped by risk (high/medium/low): what changed and why it matters, test-coverage status, suggested improvements, overall merge recommendation.
detail_level: "minimal" (standard mode inflates tokens ~6x).path/to/file.ts::ClassName.methodName; bare names return "ambiguous".list_communities + get_community in place of get_architecture_overview (~3.9M characters, overflows context).children_of for single-file structure.Target: any graph task in 5 tool calls or fewer.
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.
Develop and modify the Handsontable Angular wrapper with guidance on component lifecycle, settings updates, and NgZone, which controls change detection. It also covers standalone examples, global configuration, and the build and test workflow.
Open local or public web pages in BrowserStack Live for checks on real mobile devices or desktop browsers. The skill prepares temporary access to a local server, launches the requested session, and shares its dashboard link.
Prepare user-facing changelog entries for source code changes. The skill determines whether an entry is needed, classifies the change, writes a clear title, and uses the project CLI to create a JSON file tied to the pull request.
Work with Handsontable row and column positions by distinguishing source data, displayed order, and rendered cells. It guides index conversion and helps investigate misplaced data when sorting, filtering, hiding, or moving rows and columns.
Create Handsontable documentation examples for JavaScript, TypeScript, React, Angular, and Vue. The skill explains source files, generated JavaScript, required imports and license settings, embedding examples in guides, and checking that each framework version displays correctly.
Build Handsontable demo pages for visual regression tests, which compare screenshots for appearance changes. It guides feature routes, URL-driven display states, sample data, and decisions about testing the same feature across framework wrappers.