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

get-callee

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

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-callee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: get-callee
Source: https://github.com/opensage-agent/opensage-adk/tree/main/src/opensage/bash_tools/static_analysis/get-callee
Command: npx skills add https://github.com/opensage-agent/opensage-adk --skill get-callee

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires neo4j, and includes scripts (resource) components.

What problem does it solve?

This tool solves the difficulty of manually tracing function dependencies and execution paths within complex codebases, allowing developers to quickly identify how functions interact.

Core Features & Use Cases

  • Direct Call Analysis: Identify immediate function calls within the codebase.
  • Indirect Call Detection: Discover potential indirect execution paths that are often missed by static analysis.
  • Use Case: When refactoring a legacy module, use this tool to map out every function that calls a specific method to ensure that changes do not break downstream dependencies.

Quick Start

Use the get-callee tool to find all functions that call the process_data method within the src/main.py file.

Frequently Asked Questions about get-callee

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

FAQPage Schema
How do I trace function call graphs to find dependencies in my codebase?▼

To trace function call graphs, you can query a Neo4j database containing code analysis metadata to identify direct and indirect method invocations. This allows you to map out execution paths and dependencies.

How do I find all direct and indirect method invocations for impact analysis?▼

You can find direct and indirect method invocations by querying a pre-populated Neo4j graph database. This identifies immediate function calls and potential indirect execution paths often missed by static analysis.

Do I need a Neo4j database to map out function execution paths?▼

Yes, you need a pre-populated Neo4j graph database containing code analysis metadata. The tool queries this database to retrieve direct and indirect method invocation data for dependency mapping.

What's the best way to identify downstream callers before refactoring a legacy module?▼

The best way to identify downstream callers before refactoring is to query your Neo4j code analysis database. This maps every function that calls a specific method, ensuring changes do not break downstream dependencies.

Can static analysis detect indirect execution paths in complex codebases?▼

Static analysis alone often misses indirect execution paths, but querying a Neo4j code analysis graph detects them. It traces potential indirect execution paths by analyzing function call graphs.

What happens if my Neo4j database is not populated with code analysis metadata?▼

Without a pre-populated Neo4j database containing code analysis metadata, the tool cannot function. It relies entirely on querying this graph database to identify direct and indirect method invocations.

Related Skills

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

get-call-paths

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

Official
Advanced
typelatetypelate
6

muxt-explore-from-method

Trace Go receiver method calls to HTML templates and HTTP routes in Muxt codebases.

Official
Intermediate
opensage-agentopensage-agent
113

search-function

Locate function definitions by querying a Neo4j static analysis database.

Official
Intermediate
truongnattruongnat

nestjs-neo4j-pro

Integrates NestJS applications with Neo4j for graph data modeling, Cypher queries, and session management.

Community
Advanced