Cc-skills reindex

Re-index the GitNexus knowledge graph via CLI (gitnexus). CLI ONLY - NO MCP server exists, never use readMcpResource with gitnexus:// URIs. TRIGGERS - reindex, refresh index, update knowledge graph, $GN analyze.

install

source · Clone the upstream repo

git clone https://github.com/terrylica/cc-skills

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/terrylica/cc-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/plugins/gitnexus-tools/skills/reindex" ~/.claude/skills/terrylica-cc-skills-reindex && rm -rf "$T"

manifest: plugins/gitnexus-tools/skills/reindex/SKILL.md

source content

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.

Self-Evolving Skill: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.

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 0: Pre-flight — Ensure CLI Is Callable

The

gitnexus

binary is installed via npm/mise. The mise shim may fail if node isn't active in the current project. Run this pre-flight before any gitnexus command:

# Test if gitnexus is actually callable (not just a broken shim)
gitnexus --version 2>/dev/null || mise use node@25.8.0

All commands below run from the repo root. If multiple repos are indexed in the workspace, add

--repo <repo-name>

to specify the target. Otherwise

--repo

is optional.

Step 1: Check Current Status

gitnexus status

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

Step 2: Run Indexer

gitnexus analyze

Use

--force

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

gitnexus analyze --force

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

Step 3: Verify New Index

gitnexus 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

Post-Execution Reflection

After this skill completes, reflect before closing the task:

Locate yourself. — Find this SKILL.md's canonical path before editing.
What failed? — Fix the instruction that caused it.
What worked better than expected? — Promote to recommended practice.
What drifted? — Fix any script, reference, or dependency that no longer matches reality.
Log it. — Evolution-log entry with trigger, fix, and evidence.

Do NOT defer. The next invocation inherits whatever you leave behind.