mcpField
G
gitnexus-exploring

gitnexus-exploring

github.com/arenukvernDevelopment39447 installsUpdated 2w ago
Repository

About gitnexus-exploring

A skill for exploring indexed codebases with GitNexus, using graph-backed queries, symbol context, and execution traces to understand project structure and behavior. It is for developers investigating unfamiliar code or tracing how a feature works.

Key features

  1. 01Discover indexed repositories
  2. 02Review codebase context and freshness
  3. 03Search related execution flows
  4. 04Inspect symbol callers and callees
  5. 05Read step-by-step process traces

Use cases

  1. 01Understand an unfamiliar project structure
  2. 02Trace authentication or payment flows
  3. 03Locate database-related logic
  4. 04Inspect a symbol's callers and dependencies

MCP support

Uses GitNexus MCP resources such as `gitnexus://repo/{name}/context` and process traces, plus the `query` and `context` tools to explore code and execution flows.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/arenukvern/mcp_flutter --skill gitnexus-exploring

After installing, type/gitnexus-exploringin Claude Code to confirm it loaded.

Details

From the project README

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

Workflow

1. READ gitnexus://repos                          → Discover indexed repos
2. READ gitnexus://repo/{name}/context             → Codebase overview, check staleness
3. query({search_query: "<what you want to understand>"})  → Find related execution flows
4. context({name: "<symbol>"})            → Deep dive on specific symbol
5. READ gitnexus://repo/{name}/process/{name}      → Trace full execution flow

If step 2 says "Index is stale" → run node .gitnexus/run.cjs analyze in terminal.

Checklist

- [ ] READ gitnexus://repo/{name}/context
- [ ] query for the concept you want to understand
- [ ] Review returned processes (execution flows)
- [ ] context on key symbols for callers/callees
- [ ] READ process resource for full execution traces
- [ ] Read source files for implementation details

Resources

ResourceWhat you get
gitnexus://repo/{name}/contextStats, staleness warning (~150 tokens)
gitnexus://repo/{name}/clustersAll functional areas with cohesion scores (~300 tokens)
gitnexus://repo/{name}/cluster/{name}Area members with file paths (~500 tokens)
gitnexus://repo/{name}/process/{name}Step-by-step execution trace (~200 tokens)

Tools

query — find execution flows related to a concept:

query({search_query: "payment processing"})
→ Processes: CheckoutFlow, RefundFlow, WebhookHandler
→ Symbols grouped by flow with file locations

context — 360-degree view of a symbol:

context({name: "validateUser"})
→ Incoming calls: loginHandler, apiMiddleware
→ Outgoing calls: checkToken, getUserById
→ Processes: LoginFlow (step 2/5), TokenRefresh (step 1/3)

Example: "How does payment processing work?"

1. READ gitnexus://repo/my-app/context       → 918 symbols, 45 processes
2. query({search_query: "payment processing"})
   → CheckoutFlow: processPayment → validateCard → chargeStripe
   → RefundFlow: initiateRefund → calculateRefund → processRefund
3. context({name: "processPayment"})
   → Incoming: checkoutHandler, webhookHandler
   → Outgoing: validateCard, chargeStripe, saveTransaction
4. Read src/payments/processor.ts for implementation details

Comments

Markdown supported