Distribute as a Claude Code plugin instead of dumping files into user repos

Area

gitnexus (CLI / core / indexing / MCP server)

Problem or opportunity

npx gitnexus analyze writes files directly into the user’s repository: ∙ CLAUDE.md (~100 lines of prescriptive instructions) ∙ AGENTS.md (~100 lines, identical content) ∙ .claude/skills/gitnexus/ (6 generic skill folders) These files are not project-specific — they’re generic gitnexus tool usage instructions identical across every repo. This causes: 1. System prompt bloat — 100+ lines of gitnexus-specific rules loaded into every Claude Code session 2. Repo pollution — generic tool docs committed alongside project code 3. Conflicting instructions — “NEVER edit without running gitnexus_impact” overrides normal workflows 4. Duplicated skills — same skills exist in ~/.claude/skills/gitnexus/ (see #656)

Proposed solution

Distribute gitnexus as a Claude Code plugin using the official plugin system. The plugin structure would be: gitnexus-plugin/ ├── .claude-plugin/ │ └── plugin.json ├── skills/ │ ├── gitnexus-exploring/ │ ├── gitnexus-impact-analysis/ │ ├── gitnexus-debugging/ │ ├── gitnexus-refactoring/ │ ├── gitnexus-guide/ │ └── gitnexus-cli/ ├── hooks/ │ └── hooks.json ├── .mcp.json └── settings.json Users would install with /plugin install gitnexus — no files dumped into the repo, skills namespaced as /gitnexus:exploring, and easy to enable/disable. npx gitnexus analyze should only produce the .gitnexus/ index (the actual graph data), not context files or skills.

Alternatives considered

∙	Add --skip-context and --skip-skills flags (see #656) as a stopgap
∙	Support a .gitnexusrc config file to disable file generation

Acceptance criteria

npx gitnexus analyze no longer generates CLAUDE.md, AGENTS.md, or .claude/skills/ in user repos ∙ A gitnexus Claude Code plugin is published and installable via /plugin install ∙ Skills are namespaced (e.g. /gitnexus:exploring) ∙ Plugin includes MCP server config, hooks, and all 6 existing skills ∙ .gitnexus/ index directory remains the only repo-local artifact

Constraints

Must remain backward-compatible: users who rely on the current generated files should get a deprecation warning before removal ∙ Plugin must work without requiring npx gitnexus analyze to have been run first (MCP server should handle indexing on demand) ∙ No changes to the .gitnexus/ index format

Contribution

• I am willing to open a PR for this (may need design discussion first).