Gitnexus Cli
- 687 installs
- 45.1k repo stars
- Updated August 4, 2026
- abhigyanpatwari/gitnexus
gitnexus-cli is a Claude Code skill that documents GitNexus CLI commands for indexing Git repositories into a knowledge graph and generating wikis for developers who need agent-ready codebase context.
About
gitnexus-cli is a Claude Code skill for the GitNexus CLI that helps developers index local Git repositories into a searchable knowledge graph and manage those indexes from the terminal. The project-local runner resolves via node .gitnexus/run.cjs or auto-selects global gitnexus, pnpm dlx, or npx without requiring a global install. Running npx gitnexus analyze indexes symbols and dependencies, writes .gitnexus/meta.json, generates AGENTS.md and CLAUDE.md context files, installs per-repo agent skills, and optionally builds embeddings when symbol count stays under 50,000. gitnexus wiki generates LLM-powered module documentation from the graph, defaulting to gpt-4o-mini. Developers reach for gitnexus-cli when asked to index a repo, reanalyze after commits, check index status, clean stale indexes, or generate a repository wiki for agent workflows.
- Unified CLI for GitHub, GitLab, Bitbucket and Gitea operations
- Seamless repository creation, cloning, and synchronization across providers
- Agent-compatible commands for automated Git workflows
- Built-in authentication and permission handling for multiple remotes
Gitnexus Cli by the numbers
- 687 all-time installs (skills.sh)
- Ranked #90 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/abhigyanpatwari/gitnexus --skill gitnexus-cliAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 687 |
|---|---|
| repo stars | ★ 45.1k |
| Last updated | August 4, 2026 |
| Repository | abhigyanpatwari/gitnexus ↗ |
How do you index a repo for agent context?
Connect local Git repositories directly to multiple Git hosting platforms through a unified command-line interface.
Who is it for?
Developers using Cursor or Claude Code who want local knowledge-graph indexing and auto-generated agent context without cloud code upload.
Skip if: Developers who only need quick browser graph exploration without CLI indexing should use the GitNexus web UI instead of gitnexus-cli.
When should I use this skill?
A developer asks to index a repository, reanalyze the codebase, check GitNexus status, clean an index, or generate a wiki.
What you get
.gitnexus graph indexes, AGENTS.md and CLAUDE.md context files, generated wiki pages, and a registered global repo index.
- .gitnexus index
- AGENTS.md
- Generated wiki documentation
By the numbers
- Skips embedding generation automatically for repositories with more than 50,000 symbols
- Default gitnexus wiki model is gpt-4o-mini
Files
GitNexus CLI Commands
Commands below use node .gitnexus/run.cjs <command> — the project-local runner gitnexus analyze drops next to the index. It auto-selects an available runner at call time (global gitnexus, else pnpm dlx, else npx), so no package-manager assumption and no global install is required.
Not analyzed yet, or `node .gitnexus/run.cjs` reports `Cannot find module` (the gitignored runner is absent — e.g. a fresh clone orgit clean)? (Re)generate it withnpx gitnexus analyzefrom the project root. On npm 11.x, ifnpxcrashes during install (node.target is null), install once withnpm i -g gitnexus(thengitnexus analyze) or usepnpm --allow-build=@ladybugdb/core --allow-build=gitnexus --allow-build=tree-sitter dlx gitnexus@latest analyze. See #1939.
Commands
analyze — Build or refresh the index
node .gitnexus/run.cjs analyzeRun from the project root. This parses all source files, builds the knowledge graph, writes it to .gitnexus/, and generates CLAUDE.md / AGENTS.md context files.
| Flag | Effect |
|---|---|
--force | Force full re-index even if up to date |
--embeddings | Enable embedding generation for semantic search (off by default) |
--drop-embeddings | Drop existing embeddings on rebuild. By default, an analyze without --embeddings preserves them. |
When to run: First time in a project, after major code changes, or when gitnexus://repo/{name}/context reports the index is stale. In Claude Code, a PostToolUse hook detects staleness after git commit and git merge and notifies the agent to run analyze — the hook does not run analyze itself, to avoid blocking the agent for up to 120s and risking KuzuDB corruption on timeout.
status — Check index freshness
node .gitnexus/run.cjs statusShows whether the current repo has a GitNexus index, when it was last updated, and symbol/relationship counts. Use this to check if re-indexing is needed.
clean — Delete the index
node .gitnexus/run.cjs cleanDeletes the .gitnexus/ directory and unregisters the repo from the global registry. Use before re-indexing if the index is corrupt or after removing GitNexus from a project.
| Flag | Effect |
|---|---|
--force | Skip confirmation prompt |
--all | Clean all indexed repos, not just the current one |
wiki — Generate documentation from the graph
node .gitnexus/run.cjs wikiGenerates repository documentation from the knowledge graph using an LLM. Requires an API key (saved to ~/.gitnexus/config.json on first use).
| Flag | Effect |
|---|---|
--force | Force full regeneration |
--model <model> | LLM model (default: minimax/minimax-m2.5) |
--base-url <url> | LLM API base URL |
--api-key <key> | LLM API key |
--concurrency <n> | Parallel LLM calls (default: 3) |
--gist | Publish wiki as a public GitHub Gist |
list — Show all indexed repos
node .gitnexus/run.cjs listLists all repositories registered in ~/.gitnexus/registry.json. The MCP list_repos tool provides the same information.
After Indexing
1. Read `gitnexus://repo/{name}/context` to verify the index loaded 2. Use the other GitNexus skills (exploring, debugging, impact-analysis, refactoring) for your task
Troubleshooting
- "Not inside a git repository": Run from a directory inside a git repo
- Index is stale after re-analyzing: Restart Claude Code to reload the MCP server
- Embeddings slow: Omit
--embeddings(it's off by default) or setOPENAI_API_KEYfor faster API-based embedding
Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.272k94k
Resolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.183k193kGit Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.175k193k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.149k263k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.6k37.2k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.16.5k148How it compares
Pick gitnexus-cli for persistent local indexes and agent context files; pick browser-only graph UIs for quick one-off exploration.
FAQ
How do you run GitNexus without a global install?
gitnexus-cli uses node .gitnexus/run.cjs <command> as the project-local runner. GitNexus auto-selects an available runner at call time—global gitnexus, pnpm dlx, or npx—so agents do not need to assume a specific package manager.
What does gitnexus analyze produce?
gitnexus analyze builds a .gitnexus knowledge-graph index, writes meta.json, generates AGENTS.md and CLAUDE.md context files, installs per-repo agent skills, and optionally creates embeddings when the repository has fewer than 50,000 symbols.