ck:gkg

Indexes Git repositories to semantically navigate code and find cross-file references for Ruby, Java, Kotlin.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/hidonguyen/trade-ops --skill ck-gkg-hidonguyen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:gkg
Source: https://github.com/hidonguyen/trade-ops/tree/main/.opencode/skills/gkg
Command: npx skills add https://github.com/hidonguyen/trade-ops --skill ck-gkg-hidonguyen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Large repositories and polyglot codebases make it hard to find definitions, usages, and the impact of changes across files and projects; traditional text search and ad-hoc grep are noisy and error-prone. This Skill provides a queryable semantic index that enables precise go-to-definition, find-usages, and impact analysis to reduce refactoring risk and speed code comprehension.

Core Features & Use Cases

  • Repository Indexing: Build a persistent AST-based knowledge graph for a workspace that can be queried efficiently.
  • IDE-like Navigation: Perform go-to-definition and find-all-usages across projects for supported languages (Ruby, Java, Kotlin; partial Python/TS/JS).
  • Impact Analysis & Architecture Mapping: Identify call sites and dependency graphs before refactoring and produce repo maps or visualizations for architecture reviews.
  • Integration Points: Expose a local HTTP API and MCP tools for AI assistants to list projects, read definitions, get references, and produce token-efficient repo maps.
  • Operational Constraints: Requires a local Git repository, an indexed workspace, and a running gkg server using local KuzuDB storage.

Quick Start

Index the current repository and start the local GKG server so you can query definitions and find usages through the HTTP or MCP endpoints.

Frequently Asked Questions about ck:gkg

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

FAQPage Schema
How do I perform go-to-definition and find-usages across a large polyglot codebase?

To perform semantic code navigation across large repositories, you must build a persistent AST-based knowledge graph. This index enables precise go-to-definition and find-all-usages queries to reduce refactoring risk and speed code comprehension.

What is the best way to analyze the impact of code changes across multiple files?

Impact analysis across multiple files is best done by querying a semantic knowledge graph to identify call sites and dependency graphs. This approach replaces noisy text search and ad-hoc grep with precise cross-file reference discovery before refactoring.

Does semantic code navigation work with Ruby, Java, and Kotlin repositories?

Semantic code navigation works with Ruby, Java, and Kotlin repositories that have strong AST support. It also provides partial support for Python, TypeScript, and JavaScript to help map polyglot codebases.

Do I need a running local server to query cross-file references for my repository?

Querying cross-file references requires an initialized Git repository, a built gkg index, and a running local server. The server exposes REST and MCP endpoints using persistent KuzuDB storage under your ~/.gkg workspace.

Can AI assistants use local HTTP APIs to read definitions and map repository architecture?

AI assistants can use local HTTP APIs and MCP tools to list projects, read definitions, and get references. These integration points allow assistants to produce token-efficient repository maps for architecture reviews.

Why does text search fail to find usages and definitions in large codebases?

Text search fails in large codebases because it is noisy and error-prone when matching identical strings across different contexts. A queryable semantic index provides precise cross-file reference discovery instead of fragile pattern matching.