Verified:GitHub

ck:gkg

Perform semantic code analysis and symbol navigation across Git repositories indexed with GitLab Knowledge Graph.

Updated Aug 27, 2026

Search Tags:#knowledge-graph #impact-analysis #code-navigation #go-to-definition #semantic-analysis #find-usages #gkg

One-click install

npx skills add https://github.com/nam3886/golang-echo-boilerplate --skill ck-gkg-nam3886

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: ck:gkg
Source: https://github.com/nam3886/golang-echo-boilerplate/tree/main/.claude/skills/gkg
Command: npx skills add https://github.com/nam3886/golang-echo-boilerplate --skill ck-gkg-nam3886

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Large codebases make it hard to locate symbol definitions, discover all usages, and assess refactor impact across multiple files and languages; manual search and ad-hoc grep are slow and error-prone. GitLab Knowledge Graph (gkg) provides AST-backed indexing and a graph query layer to enable precise, IDE-like navigation and dependency analysis for AI assistants and developers.

Core Features & Use Cases

Go-to-definition: Navigate from a call site to the exact symbol definition across the indexed project.
Find usages / Impact analysis: List all references and call sites for a symbol before refactoring.
Repository indexing and visualization: Build a KuzuDB-backed graph for architecture diagrams and repo maps.
Integration for assistants: Expose MCP and HTTP endpoints so AI tools can search definitions, read implementations, and stream indexing events.
Language support: Full cross-file support for Ruby, Java, Kotlin; partial support for Python, TypeScript, and JavaScript.

Quick Start

Index the current repository with gkg, start the gkg server, and then ask to find all usages of the symbol CreateUser across the project.

Frequently Asked Questions about ck:gkg

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

FAQPage Schema

How do I do impact analysis and find usages across a large Git repository?▼

To do impact analysis and find usages across a Git repository, you need AST-backed indexing to map all symbol references and call sites. GitLab Knowledge Graph provides this by building a KuzuDB-backed graph for precise cross-file dependency tracking.

What is semantic code navigation and how does it work for multiple programming languages?▼

Semantic code navigation uses AST-based indexing to map symbol definitions and call sites across a project. It enables IDE-like go-to-definition and find-usages features for Ruby, Java, Kotlin, with partial support for Python, TypeScript, and JavaScript.

Do I need a local server to enable go-to-definition for AI assistants?▼

Yes, enabling go-to-definition for AI assistants requires an initialized Git repository, a local gkg index, and a running server. This server exposes MCP and HTTP endpoints so AI tools can search definitions and stream indexing events.

How do I index a codebase for architecture visualization and cross-file dependency mapping?▼

To index a codebase for architecture visualization, apply AST-based indexing to build a KuzuDB-backed graph. This creates a repo map of cross-file dependencies and symbol relationships, enabling precise dependency analysis and architecture diagrams.

What are the limitations of using AST-based indexing for Python, TypeScript, and JavaScript?▼

The limitation of AST-based indexing for Python, TypeScript, and JavaScript is partial language support. Unlike Ruby, Java, and Kotlin which have full cross-file support, these languages may not provide complete symbol navigation or comprehensive impact analysis.