Agent skill · software engineering · nousresearch
gitnexus-explorer
Serve an interactive codebase knowledge graph web UI.
Why this skill is useful
Adds specific commands and configuration patterns for indexing codebases into a knowledge graph that the AI wouldn't reliably generate on its own.
What it needs
Requires cloudflared, git, node installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 226,679 stars on the source repository.
What this skill does
GitNexus Explorer Index any codebase into a knowledge graph and serve an interactive web UI for exploring symbols, call chains, clusters, and execution flows. Tunneled via Cloudflare for remote access. When to Use User wants to visually explore a codebase's architecture User asks for a knowledge graph / dependency graph of a repo User wants to share an interactive codebase explorer with someone Prerequisites Node.js (v18+) — required for GitNexus and the proxy git — repo must have a .git directory cloudflared — for tunneling (auto-installed to ~/.local/bin if missing) Size Warning The web UI renders all nodes in the browser. Repos under ~5,000 files work well. Large repos (30k+ nodes) will be sluggish or crash the browser tab. The CLI/MCP tools work at any scale — only the web visualization has this limit. Steps 1. Clone and Build GitNexus (one-time setup) 2. Patch the Web UI for Remote Access The web UI defaults to localhost:4747 for API calls. Patch it to use same-origin so it works through a tunnel/proxy: File: $GITNEXUSDIR/gitnexus-web/src/config/ui-constants.ts Change: To: File: $GITNEXUSDIR/gitnexus-web/vite.config.ts Add allowedHosts: true inside the server: { } block (only needed if running dev mode instead of production build): Then build the production bundle: 3. Index the Target Repo Add --embeddings for semantic search (slower — minutes instead of seconds). The index lives in .gitnexus/ inside the repo (auto-gitignored). 4. Create the Proxy Script Write this to a file (e.g., $GITNEXUSDIR/proxy.mjs). It serves the production web UI and proxies /api/ to the GitNexus backend — same origin, no CORS issues, no sudo, no nginx. 5. Start the Services Verify: curl -s http://localhost:8888/api/repos should return the indexed repo(s). 6. Tunnel with Cloudflare (optional — for remote access) The tunnel URL (e.g., https://random-words.trycloudflare.com) is printed to stderr. Share it — anyone with the link can explore the graph. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nousresearch/gitnexus-explorer