gkg

Index codebases with AST parsing and graph databases for symbol navigation.

2|Updated Dec 24, 2025
One-click install
npx skills add https://github.com/hotriluan/alkana-dashboard --skill gkg-hotriluan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gkg
Source: https://github.com/hotriluan/alkana-dashboard/tree/main/.opencode/skills/gkg
Command: npx skills add https://github.com/hotriluan/alkana-dashboard --skill gkg-hotriluan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Semantic code analysis and symbol navigation across repositories, enabling IDE-like insights for AI assistants.

Core Features & Use Cases

  • Go-to-definition, find-usages, and impact analysis across codebases
  • Architecture visualization and RAG-enabled code understanding
  • Language-agnostic support for Ruby, Java, Kotlin, Python, and TypeScript/JavaScript

Quick Start

Index your repository and start the semantic navigation server to enable code exploration.

Frequently Asked Questions about gkg

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

FAQPage Schema
How do I enable go-to-definition and find-usages across a multi-language codebase?▼

Go-to-definition and find-usages across a multi-language codebase require AST parsing and a graph database like KuZuDB to index definitions and relationships, enabling semantic symbol navigation and impact analysis.

Can I use semantic code analysis for Ruby, Java, Kotlin, Python, and TypeScript projects?▼

Semantic code analysis supports Ruby, Java, Kotlin, Python, and TypeScript/JavaScript projects, applying AST parsing to index definitions and relationships for language-agnostic symbol navigation and architecture visualization.

How does a knowledge graph help with code navigation and impact analysis?▼

A knowledge graph helps with code navigation by indexing definitions and relationships in a graph database, enabling semantic analysis for go-to-definition, find-usages, and impact analysis across repositories.

Do I need a graph database to run architecture visualization on my repositories?▼

Yes, architecture visualization requires a graph database like KuZuDB to index definitions and relationships, utilizing AST parsing to map symbols and enable RAG-enabled code understanding across your repositories.

What's the best way to integrate symbol navigation into an AI assistant?▼

To integrate symbol navigation into an AI assistant, index your repository and start the semantic navigation server with optional API server and MCP tools, providing IDE-like insights for code exploration.

Why does semantic code indexing require AST parsing for cross-repository navigation?▼

Semantic code indexing requires AST parsing to accurately extract definitions and relationships across repositories, building a knowledge graph that enables go-to-definition, find-usages, and impact analysis for multi-language projects.