Gitnexus Exploring

abhigyanpatwari/gitnexus/.claude/skills/gitnexus-exploring

作者 abhigyanpatwariff922c0a3b0c無授權條款47K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫今天更新

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"

僅含說明Software Development Research & Analysis

AI 產生的概覽

透過查詢 GitNexus 索引中的執行流程、符號與呼叫關係，說明程式碼庫的運作方式。

功能: 引導代理依 GitNexus MCP 工作流程操作：列出已建立索引的儲存庫、讀取儲存庫情境資源、查詢與某個概念相關的執行流程，並檢視個別符號的呼叫端與被呼叫端。產出對架構與執行路徑的說明，並要求代理說明所綁定的儲存庫及索引的新鮮度。也涵蓋儲存庫清單的分頁處理與索引過期的情況。
適用情境: 適用於有人詢問某段程式碼如何運作、想了解專案結構或架構、追蹤執行流程，或探索不熟悉的程式碼庫時。也適合回答諸如某個函式被誰呼叫、驗證或付款流程如何實作之類的問題。
執行需求: 需要具備已建立索引儲存庫的 GitNexus MCP 伺服器，並能存取其資源與工具（list_repos、query、context）。索引過期時需在終端機執行 node .gitnexus/run.cjs analyze 重新分析。此技能未附帶任何指令碼。

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

Step 1 discovers what is indexed; every call after it must say which of those it means. 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.

Workflow

1. list_repos {} or READ gitnexus://repos                          → Discover indexed repos2. READ gitnexus://repo/{name}/context             → Codebase overview, check staleness3. query({search_query: "<what you want to understand>"})  → Find related execution flows4. context({name: "<symbol>"})            → Deep dive on specific symbol5. READ gitnexus://repo/{name}/process/{name}      → Trace full execution flow

1. list_repos {} or READ gitnexus://repos                          → Discover indexed repos2. READ gitnexus://repo/{name}/context             → Codebase overview, check staleness3. query({search_query: "<what you want to understand>"})  → Find related execution flows4. context({name: "<symbol>"})            → Deep dive on specific symbol5. 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. Hot-tool staleness names which index answered (branch/lastCommit) and how fresh it is (status). Re-analyze only for behind or diverged — current is identity, unknown is unmeasurable.

Checklist

- [ ] list_repos {} — bind repo; explicit repo when >1 indexed, ask if ambiguous- [ ] 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- [ ] State the repository and index freshness with the explanation

- [ ] list_repos {} — bind repo; explicit repo when >1 indexed, ask if ambiguous- [ ] 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- [ ] State the repository and index freshness with the explanation

Resources

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)

Tools

query — find execution flows related to a concept:

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

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

context — 360-degree view of a symbol:

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

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

repo is required once more than one repository is indexed, and may be omitted with a single one.

Example: "How does payment processing work?"

1. list_repos {}                             → total: 1 (my-app) — bind it   READ gitnexus://repo/my-app/context       → 918 symbols, 45 processes2. query({search_query: "payment processing"})   → CheckoutFlow: processPayment → validateCard → chargeStripe   → RefundFlow: initiateRefund → calculateRefund → processRefund3. context({name: "processPayment"})   → Incoming: checkoutHandler, webhookHandler   → Outgoing: validateCard, chargeStripe, saveTransaction4. Read src/payments/processor.ts for implementation details5. Answer, noting: Repository my-app, index current

1. list_repos {}                             → total: 1 (my-app) — bind it   READ gitnexus://repo/my-app/context       → 918 symbols, 45 processes2. query({search_query: "payment processing"})   → CheckoutFlow: processPayment → validateCard → chargeStripe   → RefundFlow: initiateRefund → calculateRefund → processRefund3. context({name: "processPayment"})   → Incoming: checkoutHandler, webhookHandler   → Outgoing: validateCard, chargeStripe, saveTransaction4. Read src/payments/processor.ts for implementation details5. Answer, noting: Repository my-app, index current

Had step 1 returned two repositories, every call above would carry repo: "my-app".

來源與署名

來源：abhigyanpatwari/gitnexus位於.claude/skills/gitnexus-exploring提交ff922c0

授權條款：無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架

Gitnexus Exploring

Exploring Codebases with GitNexus

When to Use

Bind the repository first

Workflow

Checklist

Resources

Tools

Example: "How does payment processing work?"

來源與署名

更多來自 abhigyanpatwari/gitnexus 的技能

Gitnexus Guide

Gitnexus Debugging

Gitnexus Refactoring

Gitnexus Impact Analysis

Gitnexus Cli

更多Software Development技能

Playground

M5 Onboard

Cardputer Buddy

Web Design Guidelines

Vercel React Native Skills

Vercel React Best Practices