gitnexus-cli

Build and refresh a GitNexus knowledge index for a repository.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/truongnat/emplus --skill gitnexus-cli-truongnat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitnexus-cli
Source: https://github.com/truongnat/emplus/tree/main/.claude/skills/gitnexus/gitnexus-cli
Command: npx skills add https://github.com/truongnat/emplus --skill gitnexus-cli-truongnat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitNexus helps you quickly build and refresh a searchable knowledge index of a repository so you can generate usable repo context (like CLAUDE.md/AGENTS.md) and documentation without manually studying the whole codebase.

Core Features & Use Cases

  • Index/Analyze Repos: Build or refresh the knowledge graph and write it to the .gitnexus/ directory, optionally enabling embeddings for semantic search.
  • Check Index Freshness: Verify whether the index exists and whether it is stale before attempting analysis-dependent tasks.
  • Generate Repo Wiki: Create LLM-generated documentation from the knowledge graph, useful for onboarding and engineering reference material.
  • Use Case: When you make a major refactor, re-run analyze to refresh relationships and then run wiki to regenerate documentation that matches the updated code.

Quick Start

Run the analyze command from the project root to build the index: npx gitnexus analyze.

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 to build a knowledge graph for code understanding?

To index a repository for code understanding, run the analyze command from your project root. This builds a knowledge graph in the .gitnexus/ directory, enabling downstream codebase analysis and documentation generation.

Can I generate documentation from a codebase without manually studying the code?

Yes, you can generate LLM-based documentation from a codebase using the wiki command. It uses your repository's knowledge graph to create onboarding and engineering reference material without manual code study.

How do I check if my repository index is stale before running analysis?

You can check repository index staleness by running the status check command. It verifies whether the knowledge index exists and determines if it is stale before you attempt analysis-dependent tasks.

Do I need to install any global packages to run repository indexing via npx?

No global installation is required to run repository indexing. The tool executes directly via npx, allowing you to build, refresh, and clean indexes without adding global packages to your environment.

How can I enable semantic search when analyzing my codebase?

You can enable semantic search when analyzing your codebase by passing the --embeddings flag. This enhances the knowledge graph in the .gitnexus/ directory to support semantic querying of code relationships.

Why does wiki generation require an API key in the config file?

Wiki generation requires an API key stored at ~/.gitnexus/config.json because it uses LLMs to generate documentation from the knowledge graph. This key authenticates the requests needed to produce the engineering reference material.