Skills Guide

GitNexus Reindex

VerifiedCaution

Re-index the GitNexus knowledge graph of the current repository using the CLI command 'npx gitnexus@latest analyze'. Use this after significant refactors, large merges, or when the index is stale. Optionally force a full rebuild with '--force' if the index appears corrupted.

Sby Skills Guide Bot
DevelopmentIntermediate
806/2/2026
Claude CodeCursorWindsurf
#reindex#gitnexus#knowledge-graph#cli-tool

Recommended for

Backend developerClaude CodeCode reviewCursorFrontend developerFullstack developer

Our review

Re-indexes the GitNexus knowledge graph of a repository via the CLI.

Strengths

  • Local operation with no network calls
  • Incremental or full rebuild with --force
  • Provides detailed before/after statistics

Limitations

  • Requires GitNexus to be pre-configured
  • May take 2+ minutes on large codebases (10k+ files)
  • CLI-only, no MCP integration
When to use it

After significant refactors, merging a large PR, or when the index is reported as stale.

When not to use it

For trivial changes (1-2 files) where the index is likely still current.

Security analysis

Caution
Quality score88/100

The skill uses a network-dependent command (npx) to fetch and run a third-party package. While the purpose is legitimate, this introduces a supply chain risk that requires caution.

Findings
  • •The skill instructs running 'npx gitnexus@latest', which downloads and executes JavaScript code from npm. If the package is compromised, it could introduce malicious code. No sandboxing mentioned.

Examples

Check and Reindex
Run npx gitnexus@latest status, if not current run npx gitnexus@latest analyze, then show updated stats.
Force Rebuild
The GitNexus index seems corrupted. Force reindex the repository and show the before/after stats.

name: reindex description: "Re-index the GitNexus knowledge graph via CLI (npx gitnexus@latest). CLI ONLY - NO MCP server exists, never use readMcpResource with gitnexus:// URIs. TRIGGERS - reindex, refresh index, update knowledge graph, gitnexus analyze." allowed-tools: Bash, Read model: haiku

GitNexus Reindex

CLI ONLY — no MCP server exists. Never use readMcpResource with gitnexus:// URIs.

Re-index the current repository's GitNexus knowledge graph and verify the updated stats.

When to Use

  • After significant refactors (5+ files changed)
  • When staleness hook reports index is behind
  • After merging a large PR
  • "Refresh the knowledge graph"

Workflow

Step 1: Check Current Status

Run from the repo root (the CLI auto-detects the repo from cwd):

npx gitnexus@latest status

If already current (lastCommit matches HEAD), report "Index is up to date" and stop.

Step 2: Run Indexer

npx gitnexus@latest analyze

Use --force if the index appears corrupted or if a normal analyze doesn't pick up changes:

npx gitnexus@latest analyze --force

This may take 30–120 seconds depending on codebase size.

Step 3: Verify New Index

npx gitnexus@latest status

Step 4: Report Stats

Present the updated stats:

## GitNexus Reindex Complete

| Metric      | Before | After |
| ----------- | ------ | ----- |
| Nodes       | ...    | ...   |
| Edges       | ...    | ...   |
| Communities | ...    | ...   |
| Flows       | ...    | ...   |
| Last Commit | ...    | ...   |

Index is now current with HEAD.

Notes

  • The analyze command runs locally — no network calls
  • KuzuDB database is stored in .gitnexus/ at the repo root
  • Large codebases (10k+ files) may take 2+ minutes
  • The --force flag rebuilds from scratch; without it, incremental analysis is used
Related skills

Next.js App Router Expert

Development

A skill that turns Claude into a Next.js App Router expert.

Claude CodeCursoradvanced
890
234
2,846
Admin

README Generator

Development

Creates professional and comprehensive README.md files for your projects.

claudeCursorWindsurfbeginner
259
72
821
Admin

API Documentation Writer

Development

Generates comprehensive API documentation in OpenAPI/Swagger format.

claudeCursorWindsurfintermediate
156
44
682
Admin