- Home
- Skills
- Adibfirman
- Dotfiles
- Gitnexus Cli
gitnexus-cli_skill
- Shell
2
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
3 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill adibfirman/dotfiles --skill gitnexus-cli- SKILL.md3.2 KB
Overview
This skill exposes the gitnexus-cli commands for indexing and managing a GitNexus knowledge graph from a repository. It provides simple npx-based commands to analyze a repo, check index status, clean the index, generate a wiki, and list indexed repos. Use it to build repository context files and drive other GitNexus workflows.
How this skill works
All commands run with npx so no global install is required. analyze parses source files and writes a .gitnexus/ index plus CLAUDE.md and AGENTS.md context files; status reports index freshness and counts; clean removes the index; wiki uses an LLM to generate repository documentation; list shows registered repos. Flags allow forcing operations, toggling embeddings, selecting LLM models, and controlling concurrency or scope.
When to use it
- First time setting up GitNexus for a project to create the initial index.
- After large code changes or merges to refresh the knowledge graph.
- When gitnexus://repo/{name}/context reports the index is stale.
- Before generating project documentation or a wiki from the codebase.
- To remove or reset GitNexus state when the index is corrupt or obsolete.
Best practices
- Run npx gitnexus analyze from the repository root so files are discovered correctly.
- Use --force for a full re-index when incremental updates appear stale.
- Omit --embeddings if you want faster indexing; enable embeddings only when semantic search is needed.
- Store API keys for wiki generation in ~/.gitnexus/config.json and set --model or --base-url for custom LLMs.
- Check npx gitnexus status before regenerating docs to avoid unnecessary work.
Example use cases
- Index this repo: run npx gitnexus analyze to build the graph and context files.
- Reanalyze the codebase after a major refactor with npx gitnexus analyze --force.
- Generate a project wiki with npx gitnexus wiki --model minimax/m2.5 and an API key.
- Clean a broken index locally with npx gitnexus clean or wipe all indexes with npx gitnexus clean --all.
- List every repository registered for GitNexus with npx gitnexus list for inventory or automation.
FAQ
No. All commands run via npx so no global installation is required.
Why is the index still stale after re-analyzing?
Restart the Claude Code / MCP server to pick up the updated .gitnexus index; re-run analyze with --force if issues persist.