Gitnexus Cli

This gives Claude direct access to GitNexus CLI commands for indexing and analyzing your codebase. You'll mainly use it to run analyze when you first set up a project or after major changes, check status to see if your index is stale, and occasionally clean to wipe a corrupt index. The analyze command builds a knowledge graph of your code and drops context files that other GitNexus skills rely on, so this is typically your first step. One nice detail: it uses a local runner that auto-selects between global install, pnpm, or npx, so you're not locked into a specific package manager. Just be aware that analyze can take up to two minutes on large codebases.

skills.sh installs: 932
GitHub stars: 48.4K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add abhigyanpatwari/gitnexus --skill gitnexus-cli --agent claude-code

Installs into .claude/skills of the current project.

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 bunx, else npx), so no package-manager assumption and no global install is required — including on a bun-only machine, which has no npm, npx or pnpm at all.

Not analyzed yet, or node .gitnexus/run.cjs reports Cannot find module (the gitignored runner is absent — e.g. a fresh clone or git clean)? (Re)generate it with npx gitnexus analyze from the project root, or bunx gitnexus@latest analyze on a bun-only machine. On npm 11.x, if npx crashes during install (node.target is null), install once with npm i -g gitnexus (then gitnexus analyze), or use bunx gitnexus@latest analyze, or pnpm --allow-build=@ladybugdb/core --allow-build=gitnexus --allow-build=tree-sitter dlx gitnexus@latest analyze. See #1939.