From gitkb
Use GitKB from Claude Code for local code intelligence first, with full persistent knowledge graph setup when the user wants tasks, decisions, architecture, sync, or team context. Use when the user asks about callers, callees, impact, symbols, dead code, codebase structure, GitKB setup, tasks, or knowledge management.
How this skill is triggered — by the user, by Claude, or both
Slash command
/gitkb:gitkbThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
GitKB is a local CLI for code intelligence and a persistent knowledge graph for tasks, decisions, architecture, sync, and team context. Do not assume MCP is available. Use Bash/CLI first unless the project already has full GitKB/Claude setup.
GitKB is a local CLI for code intelligence and a persistent knowledge graph for tasks, decisions, architecture, sync, and team context. Do not assume MCP is available. Use Bash/CLI first unless the project already has full GitKB/Claude setup.
Run these checks before using GitKB:
command -v git-kb
git rev-parse --show-toplevel
If git-kb is missing, guide the user to install it:
brew install gitkb/tap/gitkb
# or
curl -fsSL https://get.gitkb.com/install.sh | bash
If the current directory is not a Git repo, explain that code intelligence needs a Git repo.
.kbGitKB code intelligence works in a normal Git repo without git-kb init.
Use these commands for code questions:
git-kb code doctor
git-kb code index
git-kb code symbols
git-kb code symbols --file path/to/file
git-kb code callers "<symbol>"
git-kb code callees "<symbol>"
git-kb code impact path/to/file
git-kb code dead
git-kb code query
Run git-kb code doctor first when you need to understand index health or language support. Run git-kb code index before first analysis or after large code changes.
Use GitKB code intelligence before broad refactors, symbol renames, dead-code removal, dependency cleanup, service-edge analysis, or questions about how code flows through the repository.
Only guide full setup when the user wants persistent tasks, project memory, sync, or complete Claude integration:
git-kb init
git-kb init claude
After full setup, canonical skills and Claude assets come from git-kb init claude. Do not recreate or vendor those assets from this plugin.
MCP is supported after full KB setup today. It is not required for first value in Claude Code. If MCP is unavailable, stale, or not initialized, use the CLI fallback and continue.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub gitkb/gitkb-claude-plugin --plugin gitkb