ck:gkg
Semantic code analysis with GitLab Knowledge Graph. Use for go-to-definition, find-usages, impact analysis, architecture visualization. Supports Ruby, Java, Kotlin, Python, TypeScript/JavaScript.
Best use case
ck:gkg is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Semantic code analysis with GitLab Knowledge Graph. Use for go-to-definition, find-usages, impact analysis, architecture visualization. Supports Ruby, Java, Kotlin, Python, TypeScript/JavaScript.
Teams using ck:gkg should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/gkg/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ck:gkg Compares
| Feature / Agent | ck:gkg | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Semantic code analysis with GitLab Knowledge Graph. Use for go-to-definition, find-usages, impact analysis, architecture visualization. Supports Ruby, Java, Kotlin, Python, TypeScript/JavaScript.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# GitLab Knowledge Graph (GKG) Semantic code analysis engine using AST parsing and KuzuDB graph database. Enables IDE-like code navigation for AI assistants. **Status**: Public beta | **Requires**: Git repository | **Storage**: `~/.gkg/` ## When to Use - Find all usages of a function/class across codebase - Go-to-definition for symbols - Impact analysis before refactoring - Generate architecture diagrams - RAG-enhanced code understanding **Use repomix instead** for: quick context dumps, any-language support, remote repos, token counting. ## Quick Start ```bash # Check installation gkg --version # Index current repo gkg index # Start server (for API/MCP) gkg server start # Stop before re-indexing gkg server stop ``` ## Installation ```bash # macOS/Linux curl -fsSL https://gitlab.com/gitlab-org/rust/knowledge-graph/-/raw/main/install.sh | bash # Windows (PowerShell) irm https://gitlab.com/gitlab-org/rust/knowledge-graph/-/raw/main/install.ps1 | iex ``` ## Core Workflows ### Index and Query ```bash gkg index /path/to/project --stats gkg server start # Query via HTTP API at http://localhost:27495 ``` ### Find Symbol Usages 1. Index project: `gkg index` 2. Start server: `gkg server start` 3. Use MCP tool `get_references` or HTTP API `/api/graph/search` ### Impact Analysis 1. Index affected repos 2. Query `get_references` for changed symbols 3. Review all call sites before refactoring ## Language Support | Language | Cross-file Refs | |----------|-----------------| | Ruby | ✅ Full | | Java | ✅ Full | | Kotlin | ✅ Full | | Python | 🚧 In progress | | TypeScript | 🚧 In progress | | JavaScript | 🚧 In progress | ## References - [CLI Commands](./references/cli-commands.md) - `gkg index`, `gkg server`, `gkg remove`, `gkg clean` - [MCP Tools](./references/mcp-tools.md) - 7 tools for AI integration - [HTTP API](./references/http-api.md) - REST endpoints for querying - [Language Details](./references/language-support.md) - Supported features per language ## Key Constraints - Must stop server before re-indexing - Requires initialized Git repository - Languages not connected across repos (yet) - TS/JS/Python cross-file refs incomplete
Related Skills
ck:worktree
Create isolated git worktree for parallel development in monorepos.
ck:web-testing
Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.
ck:web-frameworks
Build with Next.js (App Router, RSC, SSR, ISR), Turborepo monorepos. Use for React apps, server rendering, build optimization, caching strategies, shared dependencies.
ck:web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
ck:watzup
Review recent changes and wrap up the current work session.
ck:use-mcp
Utilize MCP server tools with intelligent discovery and execution.
ck:ui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.
ck:ui-styling
Style UIs with shadcn/ui components (Radix UI + Tailwind CSS). Use for accessible components, themes, dark mode, responsive layouts, design systems, color customization.
ck:threejs
Build 3D web apps with Three.js (WebGL/WebGPU). 556 searchable examples, 60 API classes, 20 use cases. Actions: create 3D scene, load model, add animation, implement physics, build VR/XR. Topics: GLTF loader, PBR materials, particle effects, shadows, post-processing, compute shaders, TSL. Integrations: WebGPU, physics engines, spatial audio.
ck:test
Run unit, integration, e2e, and UI tests. Use for test execution, coverage analysis, build verification, visual regression, and QA reports.
ck:template-skill
Replace with description of the skill and when Claude should use it.
ck:team
Orchestrate Agent Teams for parallel multi-session collaboration. Use for research, implementation, review, and debug workflows requiring independent teammates.