ck:gkg

Index multi-language repositories for semantic code navigation and impact analysis.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/JoseMas68/CRMDev --skill ck-gkg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:gkg
Source: https://github.com/JoseMas68/CRMDev/tree/main/.claude/skills/gkg
Command: npx skills add https://github.com/JoseMas68/CRMDev --skill ck-gkg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Developers struggle to locate definitions, usages, and architectural relationships across large, multi-language codebases, leading to slow refactoring and limited context for AI assistance.

Core Features & Use Cases

  • Semantic code indexing across Ruby, Java, Kotlin (full support) and partial support for Python, TypeScript, JavaScript.
  • Go‑to‑definition and find‑usages powered by a graph database, enabling impact analysis before changes.
  • Architecture visualization through generated graph queries and HTTP API.
  • MCP integration that exposes tools such as list_projects, search_codebase_definitions, get_references, and repo_map for AI assistants.

Quick Start

Ask the assistant to index the repository with GKG and then retrieve the definition of a symbol using the get_definition tool.

Frequently Asked Questions about ck:gkg

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

FAQPage Schema
How do I perform semantic code navigation and impact analysis across a multi-language repository?

This Skill enables semantic code navigation and impact analysis by indexing multi-language repositories into a graph database, supporting go-to-definition, find-usages, and architecture visualization across Ruby, Java, Kotlin, and partially Python, TypeScript, and JavaScript.

Can I use graph-based code navigation for Python, TypeScript, and JavaScript repositories?

Graph-based code navigation fully supports Ruby, Java, and Kotlin repositories, while offering partial support for Python, TypeScript, and JavaScript, allowing cross-language semantic indexing and impact analysis within the same codebase.

Do I need a Git repository to generate architecture diagrams and analyze code impacts?

Yes, an initialized Git repository is required to index the codebase, generate architecture diagrams, and perform impact analysis using graph queries and the HTTP API for your multi-language projects.

How do I expose go-to-definition and find-usages tools to an AI assistant via MCP?

You can expose tools like search_codebase_definitions, get_references, list_projects, and repo_map to AI assistants by registering an MCP server, enabling the assistant to query the indexed graph database directly.

What are the limitations of using semantic analysis for large multi-language codebases?

Semantic analysis limitations include partial language support for Python, TypeScript, and JavaScript, meaning some semantic queries may be incomplete compared to full support provided for Ruby, Java, and Kotlin repositories.