graph-exploration
Explore code relationships, search, flows, communities, architecture, and refactor previews with code-review-graph.
- License 许可
- MIT
- 最近更新
- 2026-10-08
- Stars
- ★ 11
- Forks
- 3
01 前言 Front Matter
- name
- graph-exploration
- license
- MIT
- metadata
- { "disco-role": "operating" }
- description
- Explore code relationships, search, flows, communities, architecture, and refactor previews with code-review-graph.
- disable-model-invocation
- true
02 资源文件 3
- 参考文档references/architecture-and-schema.md2.2 KB
- 参考文档references/search-and-analysis.md2.6 KB
- 参考文档references/troubleshooting.md2.4 KB
03 SKILL.md 正文
Graph Exploration
Use this sub-skill when the task is to understand code structure after a graph exists: find callers or callees, search by keyword or embedding, inspect flows or communities, identify large functions, or preview safe refactors.
Start here
- Ensure the graph exists and is current.
- Ask the smallest useful query first.
- Escalate from search to graph traversal to flow/community/refactor analysis only as needed.
Read references/search-and-analysis.md for search, traversal, flow, community, architecture, and refactor workflows. Read references/architecture-and-schema.md for graph-node and edge semantics, flow/community storage, and supported query shapes. Read references/troubleshooting.md when search falls back, flows miss entry points, communities are sparse, or a refactor preview looks incomplete.
Route by task
| User task | Do this |
|---|---|
| "Who calls this function?" | query_graph_tool(pattern="callers_of", target=...) |
| "What does this function call?" | query_graph_tool(pattern="callees_of", target=...) |
| "Find tests for this symbol" | query_graph_tool(pattern="tests_for", target=...) |
| "Search for login/auth code" | semantic_search_nodes_tool or query_graph_tool depending on whether the answer is semantic or structural. |
| "Show execution paths" | list_flows_tool, then get_flow_tool or get_affected_flows_tool. |
| "Show architecture" | get_architecture_overview_tool and, if needed, list_communities_tool. |
| "Find large functions" | find_large_functions_tool. |
| "Preview a rename" | refactor_tool(mode="rename"). |
| "Find dead code" | refactor_tool(mode="dead_code"). |
Use search vs graph traversal correctly
- Use
semantic_search_nodesfor natural-language or fuzzy discovery. - Use
query_graph_toolwhen the question is about exact structural relationships. - Use
traverse_graph_toolwhen you already have a promising node and want to walk outward. - Use
get_minimal_context_toolfirst if you are unsure where to start.
Flows and communities
Flows represent execution paths, usually rooted in entry points or decorators. Communities represent structural clusters and help with architecture-level reasoning. A good exploration answer usually explains both the local symbol and the surrounding flow/community context when relevant.
Refactor previews
The safe refactor path is preview first, apply second:
refactor_tool(mode="rename", ...)orrefactor_tool(mode="dead_code", ...)- Inspect the returned edits and affected locations.
- Only then run
apply_refactor_toolif the change is intentional.
Boundaries
- For install/setup, use
install-and-setup. - For diff review and PR comments, use
review-changes. - For embeddings, custom languages, registry/daemon, wiki, and eval workflows, use
integrations-and-extensions.
Verification anchors
Native tests that ground this route include search tests, flow tests, community tests, integration tests, refactor tests, visualization tests, and status/regression tests. These are validation anchors only; do not rely on them as runtime instructions.
04 同仓库更多 Skills
obsidian-clipper-template-creator
Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.
obsidian-clipper-template-creator
Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.
python-api
Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP/mAP semantics, and source-style import diagnostics.
file-evaluation
Folder-based PASCAL VOC AP/mAP evaluation from ground-truth and detection text files.
object-detection-metrics
Guides legacy Object-Detection-Metrics PASCAL VOC AP/mAP evaluation from detection text folders and direct Python API classes.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.