gitkb
Give Claude Code the knowledge layer your agents deserve: local code intelligence, a persistent knowledge graph, task context, and team sync
Open source Repository Open in the app JSON README (API)
About
Give Claude Code the knowledge layer your agents deserve: local code intelligence, a persistent knowledge graph, task context, and team sync.
Details
- Kind
- Plugins
- Topic
- AI, RAG & memory
- Publisher
- gitkb
- Origin
- marketplace
- Category
- ferramentas
- Open pull requests
- 1
- Last push
- 2026-05-19T20:56:21Z
- Repository state
- ativo
- Language
- Shell
- Added
- 2026-08-30 01:48:58
- Updated
- 2026-08-30 01:48:58
- Origin id
gitkb/gitkb-claude-plugin/gitkb
README
# GitKB Claude Code Plugin This repository contains the GitKB marketplace plugin for Claude Code. GitKB gives Claude Code local code intelligence first: symbols, callers, callees, impact analysis, dead-code detection, language coverage, and service-edge queries through the `git-kb` CLI. Full GitKB setup adds the persistent knowledge graph for tasks, specs, decisions, architecture, and team sync. The user-facing plugin README lives at [plugin/README.md](plugin/README.md). ## Repository Layout ```text .claude-plugin/marketplace.json # Repo-level Claude marketplace manifest plugin/ # Installable Claude Code plugin payload plugin/.claude-plugin/plugin.json # Plugin manifest plugin/hooks/hooks.json # Claude hook registration plugin/scripts/ # Hook implementation plugin/skills/ # Minimal bootstrap skill tests/ # BATS tests for hook behavior Makefile # Local validation and release checks ``` ## Design Policy This plugin is a thin marketplace and bootstrap wrapper. It should not become a second copy of GitKB's canonical Claude integration. - Keep first value CLI-backed and init-free through `git-kb code ...`. - Do not require MCP or `.kb init` for code intelligence. - Do not vendor the full `.kb/skills` set generated by `git-kb init claude`. - Do not add broad `/kb-*` command files that duplicate canonical GitKB workflows. - Guide full setup through `git-kb init && git-kb init claude`. - Keep MCP positioned as full-KB behavior until code-only MCP exists. ## Prerequisites Local development uses: - `git-kb` - `bats` - `jq` - `shellcheck` - Claude Code CLI with `claude plugin validate` Optional: - `claude-plugin-validate` for standalone plugin-manifest validation: ```bash cargo install claude-plugin-validate ``` ## Development Run the normal local checks: ```bash make lint make test ``` Validate Claude marketplace and plugin manifests: ```bash make validate ``` Run the complete release gate: ```bash make release-check ``` The release gate runs executable checks, JSON checks, policy checks, ShellCheck, BATS tests, Claude plugin validation, and whitespace checks. Standalone validator support is available separately: ```bash make validate-standalone ``` `validate-standalone` checks the plugin payload with `claude-plugin-validate`. Use `make validate` for marketplace submission readiness because it validates the root marketplace manifest too. ## Manual Install Testing From this repository, add and install the local marketplace: ```bash claude plugin marketplace add . claude plugin install gitkb@gitkb ``` Then open a normal Git repository in Claude Code and ask a code intelligence question, such as: - "What calls `authenticate()`?" - "Find likely dead code." - "What's the blast radius of changing this file?" The plugin should guide Claude toward `git-kb code ...` commands without requiring `.kb init` or MCP. ## Marketplace Submission Before submission: ```bash make release-check ``` Submit the public repository link through the Claude plugin submission flow. The root `.claude-plugin/marketplace.json` points Claude Code at the installable plugin under `./plugin`. ## Versioning The plugin version is declared in: - `.claude-plugin/marketplace.json` - `plugin/.claude-plugin/plugin.json` Keep those versions in sync when publishing a new release.