Grepai Trace Graph

yoanbernabeu/grepai-skills/skills/trace/grepai-trace-graph

作者 yoanbernabeu382d40261c0d41109c6e11872574ba0be9b064d0无许可证收录于 2026年10月9日更新于 2026年10月9日

Build complete call graphs with GrepAI trace. Use this skill for recursive dependency analysis.

仅含说明Software Development
AI 生成的概览

指导使用 grepai trace graph 命令构建递归调用图，用于代码依赖与影响分析。

功能
该技能说明如何运行 grepai trace graph 生成函数依赖的递归调用图。内容涵盖深度控制、提取模式、JSON、紧凑 JSON 与 TOON 输出、循环标记，以及后处理为 Graphviz DOT 或 Mermaid 图。还提供大型图处理、复杂度跟踪和常见问题的建议。
适用场景
适用于梳理函数依赖、理解复杂代码流程、规划重构或评估改动影响。也适合需要调用图数据的代码审查与架构文档任务。
运行要求
需要带 trace graph 命令的 grepai CLI 以及已建立索引的代码库。可选后处理使用 python3、jq 和 Graphviz dot；该技能不附带脚本。

GrepAI Trace Graph

This skill covers using grepai trace graph to build complete call graphs showing all dependencies recursively.

When to Use This Skill

  • Mapping complete function dependencies
  • Understanding complex code flows
  • Impact analysis for major refactoring
  • Visualizing application architecture

What is Trace Graph?

grepai trace graph builds a recursive dependency tree:

main├── initialize│   ├── loadConfig│   │   └── parseYAML│   └── connectDB│       ├── createPool│       └── ping├── startServer│   ├── registerRoutes│   │   ├── authMiddleware│   │   └── loggingMiddleware│   └── listen└── gracefulShutdown    └── closeDB

Basic Usage

bash
grepai trace graph "FunctionName"

Example

bash
grepai trace graph "main"

Output:

🔍 Call Graph for "main"
main├── initialize│   ├── loadConfig│   └── connectDB├── startServer│   ├── registerRoutes│   └── listen└── gracefulShutdown    └── closeDB
Nodes: 9Max depth: 3

Depth Control

Limit recursion depth with --depth:

bash
# Default depth (2 levels)grepai trace graph "main"
# Deeper analysis (3 levels)grepai trace graph "main" --depth 3
# Shallow (1 level, same as callees)grepai trace graph "main" --depth 1
# Very deep (5 levels)grepai trace graph "main" --depth 5

Depth Examples

--depth 1 (same as callees):

main├── initialize├── startServer└── gracefulShutdown

--depth 2 (default):

main├── initialize│   ├── loadConfig│   └── connectDB├── startServer│   ├── registerRoutes│   └── listen└── gracefulShutdown    └── closeDB

--depth 3:

main├── initialize│   ├── loadConfig│   │   └── parseYAML│   └── connectDB│       ├── createPool│       └── ping├── startServer│   ├── registerRoutes│   │   ├── authMiddleware│   │   └── loggingMiddleware│   └── listen└── gracefulShutdown    └── closeDB

JSON Output

bash
grepai trace graph "main" --depth 2 --json

Output:

json
{  "query": "main",  "mode": "graph",  "depth": 2,  "root": {    "name": "main",    "file": "cmd/main.go",    "line": 10,    "children": [      {        "name": "initialize",        "file": "cmd/main.go",        "line": 15,        "children": [          {            "name": "loadConfig",            "file": "config/config.go",            "line": 20,            "children": []          },          {            "name": "connectDB",            "file": "db/db.go",            "line": 30,            "children": []          }        ]      },      {        "name": "startServer",        "file": "server/server.go",        "line": 25,        "children": [          {            "name": "registerRoutes",            "file": "server/routes.go",            "line": 10,            "children": []          }        ]      }    ]  },  "stats": {    "nodes": 6,    "max_depth": 2  }}

Compact JSON

bash
grepai trace graph "main" --depth 2 --json --compact

Output:

json
{  "q": "main",  "d": 2,  "r": {    "n": "main",    "c": [      {"n": "initialize", "c": [{"n": "loadConfig"}, {"n": "connectDB"}]},      {"n": "startServer", "c": [{"n": "registerRoutes"}]}    ]  },  "s": {"nodes": 6, "depth": 2}}

TOON Output (v0.26.0+)

TOON format offers ~50% fewer tokens than JSON:

bash
grepai trace graph "main" --depth 2 --toon

Note: --json and --toon are mutually exclusive.

Extraction Modes

bash
# Fast mode (regex-based)grepai trace graph "main" --mode fast
# Precise mode (tree-sitter AST)grepai trace graph "main" --mode precise

Use Cases

Understanding Application Flow

bash
# Map entire application startupgrepai trace graph "main" --depth 4

Impact Analysis

bash
# What depends on this utility function?grepai trace graph "validateInput" --depth 3
# Full impact of changing database layergrepai trace graph "executeQuery" --depth 2

Code Review

bash
# Is this function too complex?grepai trace graph "processOrder" --depth 5# Many nodes = high complexity

Documentation

bash
# Generate architecture diagram datagrepai trace graph "main" --depth 3 --json > architecture.json

Refactoring Planning

bash
# What would break if we change this?grepai trace graph "legacyAuth" --depth 3

Handling Cycles

GrepAI detects and marks circular dependencies:

main├── processA│   └── processB│       └── processA [CYCLE]

In JSON:

json
{  "name": "processA",  "cycle": true}

Large Graphs

For very large codebases, graphs can be overwhelming:

Limit Depth

bash
# Start shallowgrepai trace graph "main" --depth 2

Focus on Specific Areas

bash
# Instead of main, trace specific subsystemgrepai trace graph "authMiddleware" --depth 3

Filter in Post-Processing

bash
# Get JSON and filtergrepai trace graph "main" --depth 3 --json | jq '...'

Visualizing Graphs

Export to DOT Format (Graphviz)

bash
# Convert JSON to DOTgrepai trace graph "main" --depth 3 --json | python3 << 'EOF'import jsonimport sys
data = json.load(sys.stdin)
print("digraph G {")print("  rankdir=TB;")
def traverse(node, parent=None):    name = node.get('name') or node.get('n')    if parent:        print(f'  "{parent}" -> "{name}";')    children = node.get('children') or node.get('c') or []    for child in children:        traverse(child, name)
traverse(data.get('root') or data.get('r'))print("}")EOF

Then render:

bash
dot -Tpng graph.dot -o graph.png

Mermaid Diagram

bash
grepai trace graph "main" --depth 2 --json | python3 << 'EOF'import jsonimport sys
data = json.load(sys.stdin)
print("```mermaid")print("graph TD")
def traverse(node, parent=None):    name = node.get('name') or node.get('n')    if parent:        print(f"  {parent} --> {name}")    children = node.get('children') or node.get('c') or []    for child in children:        traverse(child, name)
traverse(data.get('root') or data.get('r'))print("```")EOF

Comparing Graph Sizes

Track complexity over time:

bash
# Get node countgrepai trace graph "main" --depth 3 --json | jq '.stats.nodes'
# Compare before/after refactoringecho "Before: $(grepai trace graph 'main' --depth 3 --json | jq '.stats.nodes') nodes"# ... refactoring ...echo "After: $(grepai trace graph 'main' --depth 3 --json | jq '.stats.nodes') nodes"

Common Issues

❌ Problem: Graph too large / timeout ✅ Solutions:

  • Reduce depth: --depth 2
  • Trace specific function instead of main
  • Use --mode fast

❌ Problem: Many cycles detected ✅ Solution: This indicates circular dependencies in code. Consider refactoring.

❌ Problem: Missing branches ✅ Solutions:

  • Try --mode precise
  • Check if files are indexed
  • Verify language is enabled

Best Practices

  1. Start shallow: Begin with --depth 2, increase as needed
  2. Focus analysis: Trace specific functions, not always main
  3. Export for docs: Use JSON for generating diagrams
  4. Track over time: Monitor node count as complexity metric
  5. Investigate cycles: Circular dependencies are code smells

Output Format

Trace graph result:

🔍 Call Graph for "main"
Depth: 3Mode: fast
main├── initialize│   ├── loadConfig│   │   └── parseYAML│   └── connectDB│       ├── createPool│       └── ping├── startServer│   ├── registerRoutes│   │   ├── authMiddleware│   │   └── loggingMiddleware│   └── listen└── gracefulShutdown    └── closeDB
Statistics:- Total nodes: 12- Maximum depth reached: 3- Cycles detected: 0
Tip: Use --json for machine-readable output     Use --depth N to control recursion depth

来源与署名

来源：yoanbernabeu/grepai-skills位于skills/trace/grepai-trace-graph提交382d402

许可证： 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架

更多来自 yoanbernabeu/grepai-skills 的技能

Grepai Trace Callers

yoanbernabeu

指导使用 grepai trace callers 命令查找调用某个函数的代码位置。

Software Development2026年10月9日

Grepai Trace Callees

yoanbernabeu

指导使用 grepai trace callees 命令列出某个函数调用的所有函数。

Software Development2026年10月9日

Grepai Storage Postgres

yoanbernabeu

配置 PostgreSQL 与 pgvector 作为 GrepAI 的存储后端，涵盖安装、调优与故障排查。

DevOps & Cloud2026年10月9日

Grepai Storage Gob

yoanbernabeu

说明如何配置 GrepAI 的 GOB 本地文件存储后端，包括设置、操作、限制与迁移。

Software Development2026年10月9日

Grepai Search Tips

yoanbernabeu

指导如何编写有效的 GrepAI 语义搜索查询，按意图而非精确名称查找代码。

Software Development2026年10月9日

Grepai Search Boosting

yoanbernabeu

配置 GrepAI 搜索分数加权，提升源码路径优先级并降低测试、文档和第三方代码的排名。

Software Development2026年10月9日

更多Software Development技能

Playground

anthropics

精选

构建自包含的交互式 HTML 演练场，包含控件、实时预览和可复制的提示词输出。

Software Development37K今天更新

M5 Onboard

anthropics

精选

通过 USB 检测 M5Stack ESP32 开发板，刷写 UIFlow 2.0 固件并安装 MicroPython 应用包。

Software Development37K今天更新

Cardputer Buddy

anthropics

精选

指导迭代 Cardputer-Adv 的 MicroPython 应用包：添加应用、通过 USB 串口推送文件、查看日志并运行 REPL 命令。

Software Development37K今天更新

Web Design Guidelines

vercel-labs

精选

依据从远程来源获取的 Web Interface Guidelines 审查 UI 代码，并以 file:line 形式报告问题。

Software Development32K5周前更新

Vercel React Native Skills

vercel-labs

精选

React Native 与 Expo 最佳实践规则，涵盖列表性能、动画、导航、UI 模式、状态与 monorepo 配置。

Software Development32K5周前更新

Vercel React Best Practices

vercel-labs

精选

Vercel 的 React 与 Next.js 性能指南，以 70 条规则的形式用于编写、审查和重构代码。

Software Development32K5周前更新