mcpField
G
gitnexus-cli

gitnexus-cli

github.com/tony363Development2056 installsUpdated 30w ago
Repository

About gitnexus-cli

A command reference skill for GitNexus CLI, covering repository indexing, status checks, cleanup, and graph-based wiki generation. It is intended for developers managing GitNexus indexes from a project directory.

Key features

  1. 01Build or refresh repository indexes
  2. 02Check index freshness
  3. 03Remove indexes and registrations
  4. 04Generate graph-based documentation
  5. 05List indexed repositories

Use cases

  1. 01Create an index for a project
  2. 02Check whether re-indexing is needed
  3. 03Remove a damaged index
  4. 04Generate repository documentation

MCP support

The CLI complements GitNexus MCP: its list command shows indexed repositories, also available through the MCP list_repos tool.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/tony363/superclaude --skill gitnexus-cli

After installing, type/gitnexus-cliin Claude Code to confirm it loaded.

Details

From the project README

GitNexus CLI Commands

All commands work via npx — no global install required.

Commands

analyze — Build or refresh the index
npx gitnexus analyze

Run 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.

FlagEffect
--forceForce full re-index even if up to date
--embeddingsEnable embedding generation for semantic search (off by default)

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 runs analyze automatically after git commit and git merge, preserving embeddings if previously generated.

status — Check index freshness
npx gitnexus status

Shows 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
npx gitnexus clean

Deletes 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.

FlagEffect
--forceSkip confirmation prompt
--allClean all indexed repos, not just the current one
wiki — Generate documentation from the graph
npx gitnexus wiki

Generates repository documentation from the knowledge graph using an LLM. Requires an API key (saved to ~/.gitnexus/config.json on first use).

FlagEffect
--forceForce 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)
--gistPublish wiki as a public GitHub Gist
list — Show all indexed repos
npx gitnexus list

Lists 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 set OPENAI_API_KEY for faster API-based embedding

Comments

Markdown supported