{
  "markdown": "# GitKB Claude Code Plugin\n\nThis repository contains the GitKB marketplace plugin for Claude Code.\n\nGitKB 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.\n\nThe user-facing plugin README lives at [plugin/README.md](plugin/README.md).\n\n## Repository Layout\n\n```text\n.claude-plugin/marketplace.json   # Repo-level Claude marketplace manifest\nplugin/                           # Installable Claude Code plugin payload\nplugin/.claude-plugin/plugin.json # Plugin manifest\nplugin/hooks/hooks.json           # Claude hook registration\nplugin/scripts/                   # Hook implementation\nplugin/skills/                    # Minimal bootstrap skill\ntests/                            # BATS tests for hook behavior\nMakefile                          # Local validation and release checks\n```\n\n## Design Policy\n\nThis plugin is a thin marketplace and bootstrap wrapper. It should not become a second copy of GitKB's canonical Claude integration.\n\n- Keep first value CLI-backed and init-free through `git-kb code ...`.\n- Do not require MCP or `.kb init` for code intelligence.\n- Do not vendor the full `.kb/skills` set generated by `git-kb init claude`.\n- Do not add broad `/kb-*` command files that duplicate canonical GitKB workflows.\n- Guide full setup through `git-kb init && git-kb init claude`.\n- Keep MCP positioned as full-KB behavior until code-only MCP exists.\n\n## Prerequisites\n\nLocal development uses:\n\n- `git-kb`\n- `bats`\n- `jq`\n- `shellcheck`\n- Claude Code CLI with `claude plugin validate`\n\nOptional:\n\n- `claude-plugin-validate` for standalone plugin-manifest validation:\n\n```bash\ncargo install claude-plugin-validate\n```\n\n## Development\n\nRun the normal local checks:\n\n```bash\nmake lint\nmake test\n```\n\nValidate Claude marketplace and plugin manifests:\n\n```bash\nmake validate\n```\n\nRun the complete release gate:\n\n```bash\nmake release-check\n```\n\nThe release gate runs executable checks, JSON checks, policy checks, ShellCheck, BATS tests, Claude plugin validation, and whitespace checks.\n\nStandalone validator support is available separately:\n\n```bash\nmake validate-standalone\n```\n\n`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.\n\n## Manual Install Testing\n\nFrom this repository, add and install the local marketplace:\n\n```bash\nclaude plugin marketplace add .\nclaude plugin install gitkb@gitkb\n```\n\nThen open a normal Git repository in Claude Code and ask a code intelligence question, such as:\n\n- \"What calls `authenticate()`?\"\n- \"Find likely dead code.\"\n- \"What's the blast radius of changing this file?\"\n\nThe plugin should guide Claude toward `git-kb code ...` commands without requiring `.kb init` or MCP.\n\n## Marketplace Submission\n\nBefore submission:\n\n```bash\nmake release-check\n```\n\nSubmit 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`.\n\n## Versioning\n\nThe plugin version is declared in:\n\n- `.claude-plugin/marketplace.json`\n- `plugin/.claude-plugin/plugin.json`\n\nKeep those versions in sync when publishing a new release.\n",
  "bytes": 3451,
  "sha": "af59b76cfb702443ac6ba476b975194d78880687c53eeadaa343db766d511ad1",
  "repo_slug": "gitkb/gitkb-claude-plugin",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/plg_gitkb_gitkb_claude_plugin_gitkb_edee3362/readme"
}