skills.rest
opensage-agent
opensage-agentOFFICIAL
Explore all skills by this author →
GitHub

get-call-paths

Query a Neo4j graph database to identify call paths between source and destination functions.

113|23|Updated Mar 23, 2026
Search Tags:#static analysis#debugging#codebase#call graph#neo4j#function tracing
One-click install
npx skills add https://github.com/opensage-agent/opensage-adk --skill get-call-paths
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: get-call-paths
Source: https://github.com/opensage-agent/opensage-adk/tree/main/src/opensage/bash_tools/static_analysis/get-call-paths-to-function
Command: npx skills add https://github.com/opensage-agent/opensage-adk --skill get-call-paths

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires argparse, json, os, sys, and includes scripts (resource) components.

What problem does it solve?

This Skill solves the difficulty of manually tracing complex execution flows in large codebases by automatically identifying call paths between a source and a destination function.

Core Features & Use Cases

  • Call Graph Analysis: Leverages Neo4j graph databases to map relationships between functions.
  • Flexible Pathfinding: Supports custom source and destination function definitions with optional file path filtering.
  • Use Case: When debugging a crash, use this tool to determine if a specific input function eventually triggers a vulnerable or problematic function deep within the call stack.

Quick Start

Use the get-call-paths skill to find the call path from the function named main in main.py to the target function process_data.

Frequently Asked Questions about get-call-paths

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace a call path between two functions in a codebase?▼

To trace a call path between functions, query a pre-populated Neo4j graph database containing method and call graph nodes. This identifies execution flows from a source to a destination function for static analysis tasks.

Do I need a Neo4j database to find function call chains?▼

Yes, you need a pre-populated Neo4j database containing method and call graph nodes. The Skill queries this graph database to execute pathfinding queries and identify call paths between source and destination functions.

Can I filter function call graph queries by file path?▼

Yes, the pathfinding queries support custom source and destination function definitions with optional file path filtering. This narrows the static analysis scope to specific files within your codebase.

What is static call graph analysis used for in debugging?▼

Static call graph analysis is used for vulnerability tracing, impact analysis, and architectural exploration. It helps determine if a specific input function eventually triggers a problematic function deep within the call stack.

How do I perform impact analysis on a large codebase?▼

You can perform impact analysis on a large codebase by querying a Neo4j database to trace execution flows from a source to a destination function. This automates the difficulty of manually tracing complex call stacks.

Related Skills

Explore More Software Engineering Skills→
sitharaj88sitharaj88
1

db-neo4j

Generate Neo4j graph models, Cypher queries, and algorithm configurations.

Community
Intermediate
aubrian-haliliaubrian-halili

explore

Trace execution paths, dependencies, and data flow in codebases.

Community
Intermediate
gaganpasupuletigaganpasupuleti

codebase-navigator

Search codebases and trace API data flows with ripgrep or ack.

Community
Intermediate
opensage-agentopensage-agent
113

get-caller

Identify direct and indirect callers of functions using Neo4j callgraph data.

Official
Intermediate