Automated summary
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
After significant refactors, merging a large PR, or when the index is reported as stale.
For trivial changes (1-2 files) where the index is likely still current.
Security analysis
CautionThe 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.
- •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
Run npx gitnexus@latest status, if not current run npx gitnexus@latest analyze, then show updated stats.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
readMcpResourcewithgitnexus://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
analyzecommand runs locally — no network calls - KuzuDB database is stored in
.gitnexus/at the repo root - Large codebases (10k+ files) may take 2+ minutes
- The
--forceflag rebuilds from scratch; without it, incremental analysis is used
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/gitnexus-reindex-mmbizk9o/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/gitnexus-reindex-mmbizk9o' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/gitnexus-reindex-mmbizk9o/download' --output '.skill-downloads/gitnexus-reindex-mmbizk9o/SKILL.md.part' && mv '.skill-downloads/gitnexus-reindex-mmbizk9o/SKILL.md.part' '.skill-downloads/gitnexus-reindex-mmbizk9o/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Bash, Read
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/gitnexus-reindex-mmbizk9o/SKILL.md' && test -s '.skill-downloads/gitnexus-reindex-mmbizk9o/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/reindex' && cp -R '.skill-downloads/gitnexus-reindex-mmbizk9o' '.claude/skills/reindex'Cursor
test -f '.skill-downloads/gitnexus-reindex-mmbizk9o/SKILL.md' && test -s '.skill-downloads/gitnexus-reindex-mmbizk9o/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/reindex' && cp -R '.skill-downloads/gitnexus-reindex-mmbizk9o' '.cursor/skills/reindex'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/gitnexus-reindex-mmbizk9o'openskills read 'gitnexus-reindex-mmbizk9o'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/gitnexus-reindex-mmbizk9o/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.