Verified:GitHub

ck:gkg

Analyze code semantics and navigate symbols using a GitLab Knowledge Graph.

Updated Apr 23, 2026

Search Tags:#impact analysis #code navigation #codebase management #semantic analysis #GitLab

One-click install

npx skills add https://github.com/snake-dev-team/snake-backlink-forge --skill ck-gkg-snake-dev-team

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: ck:gkg
Source: https://github.com/snake-dev-team/snake-backlink-forge/tree/main/.claude/skills/gkg
Command: npx skills add https://github.com/snake-dev-team/snake-backlink-forge --skill ck-gkg-snake-dev-team

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires knowledge-graph, ast-parser, kuzudb, and includes scripts (resource) and references (resource) components.

What problem does it solve?

The ck:gkg skill addresses the challenge of navigating complex codebases efficiently, providing quick access to function and class definitions, finding usages, and analyzing impacts for refactoring.

Core Features & Use Cases

Code Navigation: Go-to-definition for symbols, find all usages of functions/classes.
Impact Analysis: Conduct impact analysis before refactoring, aiding in understanding code changes.
Visualization: Generate architecture diagrams for better codebase understanding.
Use Case: When working on a large codebase and need to quickly find all occurrences of a particular method to assess the impact of changes.

Quick Start

Execute the gkg index command for your project and use the HTTP API or MCP tool to query the knowledge graph.

Frequently Asked Questions about ck:gkg

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

FAQPage Schema

How do I find all usages of a function in a large codebase for impact analysis?▼

To perform impact analysis and find all usages of a function, you can index your Git repository using the `gkg index` command and query the resulting knowledge graph to locate all occurrences. This allows you to assess refactoring impacts accurately.

How does semantic code navigation work with a GitLab Knowledge Graph?▼

Semantic code navigation with a GitLab Knowledge Graph works by indexing your Git repository to build a graph of code symbols. It facilitates IDE-like browsing for AI-assisted development, enabling go-to-definition lookups and usage queries across multiple programming languages.

Do I need a Git repository to use semantic code analysis for AI-assisted development?▼

Yes, you need a Git repository to use this semantic code analysis. The skill requires a Git repository to index the codebase and build the knowledge graph needed for navigating symbols and analyzing refactoring impacts.

Can I generate architecture diagrams from my codebase to understand code structure?▼

Yes, you can generate architecture diagrams to understand your code structure. Once your project is indexed in the knowledge graph, you can visualize the architecture to gain better insights into the codebase and its dependencies.

What is the best way to assess refactoring impact before modifying a complex codebase?▼

The best way to assess refactoring impact is to conduct a semantic impact analysis using a knowledge graph. By indexing your codebase and querying for all usages of the targeted classes or methods, you can thoroughly understand the potential effects of code changes.

What are the limitations of using a knowledge graph for code navigation?▼

A limitation of using a knowledge graph for code navigation is that it requires a Git repository and an initial indexing step via `gkg index` before queries can be made. It relies on semantic analysis, so the accuracy depends on the underlying AST parser and KuzuDB dependencies.