ck:gkg

To find symbol usages and definitions across multiple languages, you can use semantic code analysis to map your repository into a knowledge graph. This enables cross-language go-to-definition and find-usages queries for Ruby, Java, Kotlin, Python, and TypeScript/JavaScript.

The best way to visualize codebase architecture and perform impact analysis is by parsing your codebase into a graph database. This maps semantic relationships, allowing you to safely identify refactoring impacts and visualize structural dependencies across your project.

Yes, semantic code navigation works with Ruby, Java, Kotlin, Python, and TypeScript/JavaScript in the same repository. It applies AST parsing across these languages to support unified cross-language navigation and impact analysis.

To set up a codebase knowledge graph, initialize a Git repository and run the provided installation and server workflows. The system uses AST parsing to extract semantic code data and stores it in a KuzuDB graph database backend.

Yes, you need a Git repository to run cross-language code analysis and locate symbol definitions. The semantic analysis process requires a Git repository to parse the codebase and build the knowledge graph for navigation.

Yes, you can use architecture visualization to track cross-language dependencies in a polyglot codebase. By applying AST parsing and storing relationships in a graph database, the system maps connections across Ruby, Java, Kotlin, Python, and TypeScript/JavaScript.