gitnexus-cli

Runs GitNexus CLI commands to analyze, index, and document code repositories.

1|Updated Jul 27, 2023
One-click install
npx skills add https://github.com/AlexTheGuitarGuy/.dotfiles --skill gitnexus-cli-alextheguitarguy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gitnexus-cli
Source: https://github.com/AlexTheGuitarGuy/.dotfiles/tree/main/claude/.claude/skills/gitnexus-cli
Command: npx skills add https://github.com/AlexTheGuitarGuy/.dotfiles --skill gitnexus-cli-alextheguitarguy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing a GitNexus code knowledge graph requires knowing the right CLI commands and flags for indexing, checking freshness, cleaning stale indexes, and generating documentation. This Skill provides the exact command reference so an agent can run GitNexus operations correctly on any machine, including bun-only environments without npm. ## Core Features & Use Cases - Index Management: Build or refresh the repository knowledge graph with analyze, check freshness with status, and delete corrupt indexes with clean. - Documentation Generation: Create wiki documentation from the knowledge graph using HTTP LLM providers or local CLI logins like Claude, Cursor, or Codex. - Registry Listing: Show all indexed repositories registered in the global GitNexus registry. - Use Case: After cloning a repo, ask the agent to index the codebase; it runs node .gitnexus/run.cjs analyze, then you can use the exploring, debugging, and impact-analysis skills against the fresh index. ## Quick Start Ask the agent to index this repository with GitNexus and then check the index status.

Frequently Asked Questions about gitnexus-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I index a repository with GitNexus?▼

Run node .gitnexus/run.cjs analyze from the project root to parse source files and build the knowledge graph. If the runner is missing, regenerate it with npx gitnexus analyze or bunx gitnexus@latest analyze on bun-only machines.

How to generate wiki documentation from a codebase knowledge graph?▼

Run node .gitnexus/run.cjs wiki after indexing. It uses an LLM provider such as minimax, openai, or local CLI logins like claude, cursor, or codex, with flags for model, language, concurrency, and retries.

Does GitNexus work on a machine without npm or npx?▼

Yes, the project-local runner auto-selects an available runner at call time, falling back through global gitnexus, pnpm dlx, bunx, and npx. On bun-only machines use bunx gitnexus@latest analyze to bootstrap.

Why does GitNexus report the index is stale after re-analyzing?▼

Running MCP and serve processes periodically check for a published replacement index and reopen it without restarting. MCP checks are throttled to once every five seconds, so a tool call before the next check briefly uses the previous index.

When should I use gitnexus clean before re-indexing?▼

Use clean when the index is corrupt or after removing GitNexus from a project. It deletes the .gitnexus directory and unregisters the repo from the global registry, with --force to skip confirmation and --all to clean every indexed repo.