What problem does it solve? Keeping a codebase knowledge graph fresh and usable is manual and error-prone: developers forget to re-index after refactors, trust stale graph output, or hit cryptic failures like duplicated primary key errors. This Skill provides the exact GitNexus CLI commands, flags, and troubleshooting steps to manage the index lifecycle correctly. ## Core Features & Use Cases - Index Management: Build or refresh the repository knowledge graph with npx gitnexus analyze, including embedding generation and forced re-indexing options. - Freshness Verification: Check index status and compare the indexed commit against HEAD to detect stale graphs before trusting any output. - Documentation Generation: Generate a wiki from the knowledge graph using an LLM, with configurable model, concurrency, and optional GitHub Gist publishing. - Use Case: After merging a large feature branch, run npx gitnexus status, notice the indexed commit differs from HEAD, then run npx gitnexus analyze to rebuild the graph before using exploration or impact-analysis tools. ## Quick Start Ask the assistant to index this repository with GitNexus and verify the index is fresh before running any graph-based analysis.