Gitnexus Exploring

This is for navigating unfamiliar codebases when you need to understand how something actually works. It connects to GitNexus's execution flow analysis, so instead of grepping through files hoping to piece together "how does auth work," you can query for concepts and get back traced execution paths showing what calls what. The gitnexus_context tool gives you a 360-degree view of any function with its callers, callees, and which flows it participates in. Most useful when onboarding to a new project or debugging something that spans multiple files. Just note you'll need to run npx gitnexus analyze first if the index is stale.

skills.sh installs: 1.9K
GitHub stars: 48.4K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add abhigyanpatwari/gitnexus --skill gitnexus-exploring --agent claude-code

Installs into .claude/skills of the current project.

Files

Exploring Codebases with GitNexus

When to Use

"How does authentication work?"
"What's the project structure?"
"Show me the main components"
"Where is the database logic?"
Understanding code you haven't seen before

Bind the repository first

Bind once per session using a confirmed registry name/path or configured MCP default; reuse it. Call list_repos {} when the target is not yet known, not before every question. Never guess the registry name from the checkout directory. With one indexed repository, use the examples below as written. With more than one, pass repo on every call: an omitted repo normally errors, but under an MCP policy with a configured default it resolves to that default silently. If you cannot tell which repository is meant, stop and ask. Report the bound repository and index freshness alongside your explanation.

list_repos is paginated, so page with offset: pagination.nextOffset until hasMore is false before concluding a repository is absent.