Verified:GitHub

ck:gkg

Find symbol definitions and cross-file usages across repositories via semantic analysis.

Updated Aug 27, 2026

Search Tags:#knowledge graph #impact analysis #code navigation #AST parsing #go-to-definition #semantic code analysis #kuzuDB

Ready to run

npx skills add https://github.com/MinhQuyen274/smartify --skill ck-gkg-minhquyen274

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ck:gkg
Source: https://github.com/MinhQuyen274/smartify/tree/main/Frontend_PROJECT_Figma/.opencode/skills/gkg
Command: npx skills add https://github.com/MinhQuyen274/smartify --skill ck-gkg-minhquyen274

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the challenge of understanding and navigating a large codebase by letting you find definitions, usages, and refactoring impact using semantic analysis rather than brittle text search.

Core Features & Use Cases

Semantic go-to-definition and find-usages across supported languages to quickly locate what a symbol refers to and where it’s used.
Impact analysis before refactoring so you can review all call sites and dependencies before making changes.
Architecture visualization support using relationships discovered in the knowledge graph to help explain system structure to humans and AI.
Use for code navigation workflows such as RAG-enhanced code understanding, symbol discovery, and dependency exploration.

Quick Start

Index your repository by starting the GKG server workflow and then querying symbol relationships for a specific project path.

Frequently Asked Questions about ck:gkg

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

FAQPage Schema

How does semantic code analysis find cross-file symbol usages in a large repository?▼

Semantic code analysis finds cross-file symbol usages by applying AST-based extraction to parse the repository, indexing the relationships in a graph database, and querying those definitions and call sites via HTTP or MCP tools.

What is the best way to perform impact analysis before refactoring a codebase?▼

Impact analysis before refactoring is best performed by querying a semantic knowledge graph to review all symbol call sites and dependencies, ensuring you understand the full scope of changes before modifying the code.

How do I index my repository for go-to-definition and code navigation workflows?▼

To index your repository for go-to-definition and code navigation, you need to start the GKG server workflow, which builds the AST-based knowledge graph using KuzuDB so you can query symbol relationships for a specific project path.

Does semantic code analysis work better than text search for locating symbol definitions?▼

Semantic code analysis works better than text search for locating symbol definitions because it understands the code structure rather than relying on brittle string matching, allowing it to accurately find what a symbol refers to across files.

Can I use a knowledge graph to prepare architecture diagrams and explain system structure?▼

Yes, you can use a knowledge graph to support architecture visualization by discovering and extracting the relationships between components, which helps explain the system structure to both humans and AI during diagram preparation.

What are the limitations of using AST parsing for semantic code analysis?▼

A limitation of using AST parsing for semantic code analysis is that it relies on proper indexing via the GKG CLI and requires supported languages, meaning unsupported syntax or unindexed files will not be captured in the graph queries.