.claude/skills/gitnexus/gitnexus-exploring/SKILL.md
Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"
npx skillsauth add Vero-Ventures/fuzzycat gitnexus-exploringInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
1. READ gitnexus://repos → Discover indexed repos
2. READ gitnexus://repo/{name}/context → Codebase overview, check staleness
3. gitnexus_query({query: "<what you want to understand>"}) → Find related execution flows
4. gitnexus_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
npx gitnexus analyzein terminal.
- [ ] READ gitnexus://repo/{name}/context
- [ ] gitnexus_query for the concept you want to understand
- [ ] Review returned processes (execution flows)
- [ ] gitnexus_context on key symbols for callers/callees
- [ ] READ process resource for full execution traces
- [ ] Read source files for implementation details
| Resource | What you get |
| --------------------------------------- | ------------------------------------------------------- |
| gitnexus://repo/{name}/context | Stats, staleness warning (~150 tokens) |
| gitnexus://repo/{name}/clusters | All 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) |
gitnexus_query — find execution flows related to a concept:
gitnexus_query({query: "payment processing"})
→ Processes: CheckoutFlow, RefundFlow, WebhookHandler
→ Symbols grouped by flow with file locations
gitnexus_context — 360-degree view of a symbol:
gitnexus_context({name: "validateUser"})
→ Incoming calls: loginHandler, apiMiddleware
→ Outgoing calls: checkToken, getUserById
→ Processes: LoginFlow (step 2/5), TokenRefresh (step 1/3)
1. READ gitnexus://repo/my-app/context → 918 symbols, 45 processes
2. gitnexus_query({query: "payment processing"})
→ CheckoutFlow: processPayment → validateCard → chargeStripe
→ RefundFlow: initiateRefund → calculateRefund → processRefund
3. gitnexus_context({name: "processPayment"})
→ Incoming: checkoutHandler, webhookHandler
→ Outgoing: validateCard, chargeStripe, saveTransaction
4. Read src/payments/processor.ts for implementation details
tools
Manage Vercel deployments via CLI. Check deployment status, view logs, manage environment variables, inspect domains, trigger builds, and debug production issues. Use for any deployment or hosting task.
development
Manage Twilio SMS service via REST API. Send test messages, check message logs, inspect phone numbers, check account balance, and debug SMS delivery issues. Use for any SMS/Twilio administration task.
tools
Manage Supabase projects via CLI and Management API. List projects, check auth config, manage users, update settings, query databases, and inspect project health. Use for any Supabase administration task.
development
Interact with Stripe via REST API. List customers, payments, payouts, connected accounts, check balances, view webhook events, and manage Stripe Connect. Use for any Stripe administration, debugging, or data inspection task.