gitnexus-exploring

Explores indexed codebases with GitNexus to trace execution flows and explain architecture.

1|Updated Jul 27, 2023
One-click install
npx skills add https://github.com/AlexTheGuitarGuy/.dotfiles --skill gitnexus-exploring-alextheguitarguy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gitnexus-exploring
Source: https://github.com/AlexTheGuitarGuy/.dotfiles/tree/main/claude/.claude/skills/gitnexus-exploring
Command: npx skills add https://github.com/AlexTheGuitarGuy/.dotfiles --skill gitnexus-exploring-alextheguitarguy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Understanding an unfamiliar codebase is slow when you have to grep through files manually. This Skill uses the GitNexus index to answer questions like "How does authentication work?" or "What calls this function?" by surfacing execution flows, symbol relationships, and functional clusters directly. ## Core Features & Use Cases - Repository binding and freshness checks: Discovers indexed repositories via list_repos, handles multi-repo ambiguity, and warns when the index is stale. - Concept-to-flow search: The query tool maps a natural-language concept (e.g., "payment processing") to related execution flows and grouped symbols. - 360-degree symbol inspection: The context tool shows incoming calls, outgoing calls, and the processes a symbol participates in. - Use Case: A developer joins a new project and asks "How does payment processing work?" The Skill binds the repo, queries for the concept, traces CheckoutFlow and RefundFlow step by step, and reads the relevant source files to produce a grounded explanation. ## Quick Start Ask the assistant to explain how a specific feature works in your codebase, for example "How does authentication work in this project?"

Frequently Asked Questions about gitnexus-exploring

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

FAQPage Schema
How do I understand how a feature works in an unfamiliar codebase?▼

Bind the indexed repository with list_repos, read the repo context resource, then run a query with the concept you want to understand. Follow up with context on key symbols and read the process resource for full execution traces.

How to trace what calls a function in GitNexus?▼

Use the context tool with the symbol name, for example context({name: "validateUser"}). It returns incoming calls, outgoing calls, and the execution processes the symbol participates in, with file locations.

What should I do when the GitNexus index is stale?▼

Run node .gitnexus/run.cjs analyze in the terminal to rebuild the index. The repo context resource shows a staleness warning, and you should report index freshness alongside any explanation you give.

Do I need to pass the repo parameter on every GitNexus call?▼

With a single indexed repository, repo can be omitted. Once more than one repository is indexed, pass repo on every call, since an omitted repo normally errors or silently resolves to a configured default.

Why does list_repos not show my repository?▼

list_repos is paginated, so a repository may be on a later page. Page through results using offset: pagination.nextOffset until hasMore is false before concluding the repository is absent.