How do I install the Gitnexus CLI skill?

Run npx skillmds@latest add none9527/gitnexus-cli in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gitnexus CLI safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gitnexus CLI?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gitnexus CLI free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gitnexus CLI?

none9527 (@none9527) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gitnexus CLI by none9527 — Agent Skill

Name: Gitnexus CLI
Author: none9527

Gitnexus CLI

Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"

none9527 c9e0af3 3.4 KB Updated Sep 17, 2026

File contents

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.

Flag	Effect
`--force`	Force full re-index even if up to date
`--embeddings`	Enable 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.

Flag	Effect
`--force`	Skip confirmation prompt
`--all`	Clean 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).

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

npx gitnexus list

Lists all repositories registered in ~/.gitnexus/registry.json. The MCP list_repos tool provides the same information.

After Indexing

Read gitnexus://repo/{name}/context to verify the index loaded
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

---name: gitnexus-clidescription: Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"---# GitNexus CLI CommandsAll commands work via `npx` — no global install required.## Commands### analyze — Build or refresh the index```bashnpx 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.| Flag | Effect || -------------- | ---------------------------------------------------------------- || `--force` | Force full re-index even if up to date || `--embeddings` | Enable 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```bashnpx 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```bashnpx 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.| Flag | Effect || --------- | ------------------------------------------------- || `--force` | Skip confirmation prompt || `--all` | Clean all indexed repos, not just the current one |### wiki — Generate documentation from the graph```bashnpx gitnexus wiki```Generates 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```bashnpx gitnexus list```Lists all repositories registered in `~/.gitnexus/registry.json`. The MCP `list_repos` tool provides the same information.## After Indexing1. **Read `gitnexus://repo/{name}/context`** to verify the index loaded2. 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

Frequently asked questions