gitnexus-explorer

Index a local codebase into a GitNexus knowledge graph with a web UI.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/big4council-prog/b4c-agent --skill gitnexus-explorer-big4council-prog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitnexus-explorer
Source: https://github.com/big4council-prog/b4c-agent/tree/main/optional-skills/research/gitnexus-explorer
Command: npx skills add https://github.com/big4council-prog/b4c-agent --skill gitnexus-explorer-big4council-prog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It helps you turn a codebase into a navigable knowledge graph so you can visually understand architecture, symbol relationships, and execution flow without manually reading thousands of files.

Core Features & Use Cases

  • Codebase indexing into a knowledge graph: Indexes a target repository using GitNexus and stores the results in the repo’s .gitnexus/ directory.
  • Interactive web visualization: Serves an in-browser UI to explore symbols, call chains, clusters, and dependency/execution structures.
  • Remote sharing via Cloudflare tunnel: Enables access beyond localhost using a production build plus a lightweight Node proxy to avoid host/CORS issues.
  • Optional semantic search: Supports embeddings for natural-language queries over the indexed content (slower on large repos).

Quick Start

Clone the GitNexus web UI, index your target repository with npx gitnexus analyze --skip-agents-md, then start the API backend with npx gitnexus serve and launch the bundled static+API proxy using node scripts/proxy.mjs to open the explorer in your browser.

Frequently Asked Questions about gitnexus-explorer

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

FAQPage Schema
How do I visualize a codebase as a knowledge graph for architecture discovery?

Yes, you can inspect call chains and dependency execution structures by indexing the repository into a GitNexus knowledge graph and navigating the visual relationships exposed in the in-browser web interface.

How do I set up and start the GitNexus web UI for repository indexing?

To start the web UI, run npx gitnexus analyze on your target repository, start the backend with npx gitnexus serve, then launch the bundled static and API proxy using node scripts/proxy.mjs to open the explorer.

Can I share a browsable code graph remotely without hosting it on a public server?

Yes, the explorer supports optional semantic search using embeddings, allowing you to run natural-language queries over the indexed content to find specific symbols and relationships within the codebase.

Do I need Node.js and git history to index a repository with GitNexus?

Yes, you need Node.js installed to run GitNexus and the web proxy, and the target repository must be a local git repository with .git history to successfully index the codebase into the knowledge graph.

Are there limitations when using semantic search on large codebases?

Yes, a known limitation is that optional semantic search via embeddings runs slower on large repositories, making natural-language queries over the indexed content potentially delayed for extensive codebases.