search-function

Locate function definitions by querying a Neo4j static analysis database.

113|23|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/opensage-agent/opensage-adk --skill search-function
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: search-function
Source: https://github.com/opensage-agent/opensage-adk/tree/main/src/opensage/bash_tools/static_analysis/search-function
Command: npx skills add https://github.com/opensage-agent/opensage-adk --skill search-function

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill solves the challenge of navigating large, complex codebases by allowing you to instantly find the exact file, line numbers, and implementation details of any specific function.

Core Features & Use Cases

  • Codebase Navigation: Quickly jump to function definitions without manual searching or IDE indexing delays.
  • Static Analysis: Retrieve function metadata including file paths and line ranges directly from the project's graph database.
  • Use Case: When debugging a complex system, use this tool to find the implementation of a specific method across a large repository to understand its logic and dependencies.

Quick Start

Use the search-function skill to find the definition and code snippet for the function named calculate_metrics.

Frequently Asked Questions about search-function

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

FAQPage Schema
How do I find function definitions in a large codebase quickly?

To find function definitions rapidly, query a pre-indexed Neo4j graph database containing static analysis data to retrieve exact file paths and line numbers for specific methods without manual searching.

Do I need a Neo4j database to perform graph-based static analysis for code search?

Yes, graph-based static analysis for code search requires a pre-indexed Neo4j database populated with method nodes containing associated file paths and line information to enable rapid codebase navigation.

What's the best way to navigate codebase architecture when debugging complex software?

Navigating codebase architecture during debugging is best handled by using a code search tool to instantly locate specific method implementations across large repositories and understand their logic and dependencies.

Can I use static analysis to get file paths and line numbers for specific methods?

Yes, static analysis retrieves function metadata including exact file paths and line ranges directly from the project's graph database to facilitate rapid code navigation and architectural understanding.

Why does code search require a pre-indexed database instead of scanning files directly?

Code search requires a pre-indexed database to avoid IDE indexing delays and manual searching, allowing instant location of function definitions by querying pre-computed method nodes and associated metadata.