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

get-caller

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This tool solves the difficulty of manually tracing function dependencies and execution paths in large, complex codebases by providing an automated way to identify who calls a specific function.

Core Features & Use Cases

  • Callgraph Traversal: Identifies both direct and indirect function calls using graph-based analysis.
  • Contextual Filtering: Allows narrowing down search results by specifying file paths to reduce noise in large projects.
  • Use Case: When refactoring a legacy function, use this tool to instantly discover every location in the codebase that relies on it, ensuring you understand the impact of your changes before modifying the code.

Quick Start

Use the get-caller skill to find all functions that call the process_data method within the main application directory.

Frequently Asked Questions about get-caller

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

FAQPage Schema
How do I trace all callers of a specific function in a large codebase?▼

To trace callers of a specific function in a large codebase, this skill analyzes function call graphs to identify both direct and indirect callers. It queries structured callgraph data to automate dependency mapping and reveal execution paths.

Do I need a Neo4j database to perform callgraph traversal and impact analysis?▼

Yes, you need a Neo4j database to perform callgraph traversal. The tool requires Neo4j database connectivity to query structured callgraph data that was previously generated by static analysis tools.

Can I filter callgraph search results to specific file paths in my project?▼

Yes, you can filter callgraph search results by specifying file paths. Contextual filtering allows you to narrow down search results within large projects, which reduces noise and helps focus impact analysis on relevant directories.

What is the best way to analyze indirect function dependencies before refactoring legacy code?▼

The best way to analyze indirect function dependencies before refactoring legacy code is using graph-based callgraph traversal. It instantly discovers every direct and indirect location relying on a function, ensuring you understand the full impact of modifications.

Why does static analysis for function calls require structured callgraph data?▼

Static analysis for function calls requires structured callgraph data because the tool queries a graph database to map complex execution paths. Without this structured data, identifying indirect callers across a large-scale software repository would require manual tracing.

Related Skills

Explore More Software Engineering Skills→
opensage-agentopensage-agent
113

get-callee

Queries a Neo4j database to analyze direct and indirect function call graphs.

Official
Intermediate
CloudyWingCloudyWing

context-map

Generate change impact analyses and dependency maps for codebase modifications.

Community
Intermediate
opensage-agentopensage-agent
113

joern-slice

Extract program slices for specific functions using Joern static analysis.

Official
Intermediate
pckienuitpckienuit

codegraph

Find code symbols and trace dependency paths in a repository.

Community
Intermediate