gitnexus-index

Create, update, and repair GitNexus code indexes for repositories.

2|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/HACK-WU/skills --skill gitnexus-index-hack-wu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitnexus-index
Source: https://github.com/HACK-WU/skills/tree/main/skills/gitnexus-index
Command: npx skills add https://github.com/HACK-WU/skills --skill gitnexus-index-hack-wu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gitnexus, and includes references (resource) components.

What problem does it solve? When an AI agent needs to query a codebase through GitNexus MCP, the repository must first have a fresh, valid index. This Skill removes the operational guesswork of creating indexes for new repositories, updating stale ones after code changes, and repairing corrupted indexes (broken full-text search, vector dimension mismatches, incomplete query results). ## Core Features & Use Cases - Environment Detection and Runner Resolution: Checks for a project-local runner, global CLI, or npx fallback before running any indexing command, and verifies the target is a Git repository. - Status-Driven Indexing Decisions: Uses gitnexus status and gitnexus list to decide between first-time creation, incremental update, forced full rebuild, or targeted repair, avoiding wasteful full re-indexing. - Repair and Validation Workflow: Maps specific failures to fixes (--force, --repair-fts, --embeddings --drop-embeddings) and verifies index freshness after every operation. - Use Case: You hand an AI agent a newly cloned monorepo. The agent detects no existing index, configures .gitnexusignore to exclude node_modules and dist, runs gitnexus analyze, and confirms via gitnexus status that the index is fresh before answering code questions. ## Quick Start Ask the AI to create or update the GitNexus code index for the current repository and confirm the index is fresh.

Frequently Asked Questions about gitnexus-index

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a GitNexus code index for a repository?

Run gitnexus analyze in the repository root to build the index. The first run performs full analysis including Tree-sitter parsing, cross-file reference resolution, and hybrid search indexing; later runs update incrementally.

How do I update a stale GitNexus index after code changes?

Run gitnexus status to check freshness, then run gitnexus analyze for an incremental update that only re-parses changed files. Use gitnexus list and status afterward to confirm the index is no longer stale.

Can GitNexus index a directory that is not a Git repository?

Yes, use gitnexus analyze --skip-git to index a plain folder as the index root, skipping parent git-root discovery. Without this flag, the tool expects a Git repository.

Why are GitNexus query results incomplete or the index corrupted?

Incomplete results usually mean a stale or inconsistent index; run gitnexus analyze --force for a full rebuild. For full-text search issues only, use --repair-fts, and for vector dimension mismatches use --embeddings --drop-embeddings.

How do I speed up indexing for large repositories?

Add --skip-embeddings to disable semantic search, raise GITNEXUS_MAX_FILE_SIZE to skip large files, and create a .gitnexusignore file excluding node_modules, dist, and build directories.

What should I do when the gitnexus command is not found?

The skill resolves runners in order: a project-local .gitnexus/run.cjs, the global gitnexus CLI, then npx gitnexus as a fallback. If none work, install the CLI with npm install -g gitnexus.