Gitnexus Debugging

abhigyanpatwari/GitNexus/gitnexus-cursor-integration/skills/gitnexus-debugging

作者 abhigyanpatwari50aa4be3b2c2c9a1561fc44878e5d8f87b99d16e无许可证47K 个星标收录于 2026年10月9日更新于 2026年10月9日仓库今天更新

Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug"

仅含说明Software Development

AI 生成的概览

指导使用 GitNexus 代码图工具进行调试与错误追踪，定位根本原因。

功能: 该技能提供一套排查缺陷、错误和异常行为的工作流程，使用 GitNexus MCP 工具。流程包括先绑定正确的代码仓库、按错误文本查询、查看可疑符号的调用方与被调用方、追踪执行流，以及运行自定义 Cypher 调用链查询。最终产出包含仓库与索引新鲜度的根本原因诊断，并针对错误返回值、间歇性失败、性能问题和回归等常见症状给出调试模式。
适用场景: 当用户询问某处为何失败、错误来自哪里、谁调用了某个方法，或希望追踪缺陷与异常行为时使用。适用于在已建立索引的仓库中调查错误、500 响应、间歇性失败和近期回归。
运行要求: 需要访问 GitNexus MCP 工具（list_repos、query、context、cypher、trace、detect_changes）以及已建立索引的仓库；索引过期时可能需要在终端重新分析。该技能不附带脚本，仅为指令。

Debugging with GitNexus

When to Use

"Why is this function failing?"
"Trace where this error comes from"
"Who calls this method?"
"This endpoint returns 500"
Investigating bugs, errors, or unexpected behavior

Bind the repository first

A root cause traced in the wrong repository is a wrong root cause.

Call list_repos {} before the first tool call. 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. This matters most for cypher, whose statement carries no in-band hint of which database it ran against.

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

A stale index describes the code from before your bug, so refresh before trusting a trace, and state the repository and index freshness with the diagnosis.

Workflow

0. list_repos {}                                          → Bind repo1. query({search_query: "<error or symptom>"})            → Find related execution flows2. context({name: "<suspect>"})                    → See callers/callees/processes3. READ gitnexus://repo/{name}/process/{name}                → Trace execution flow4. cypher({statement: "MATCH path..."})                 → Custom traces if needed

0. list_repos {}                                          → Bind repo1. query({search_query: "<error or symptom>"})            → Find related execution flows2. context({name: "<suspect>"})                    → See callers/callees/processes3. READ gitnexus://repo/{name}/process/{name}                → Trace execution flow4. cypher({statement: "MATCH path..."})                 → Custom traces if needed

If "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- [ ] Understand the symptom (error message, unexpected behavior)- [ ] query for error text or related code- [ ] Identify the suspect function from returned processes- [ ] context to see callers and callees- [ ] Trace execution flow via process resource if applicable- [ ] cypher for custom call chain traces if needed- [ ] Read source files to confirm root cause- [ ] State the repository and index freshness with the diagnosis

- [ ] list_repos {} — bind repo; explicit repo when >1 indexed, ask if ambiguous- [ ] Understand the symptom (error message, unexpected behavior)- [ ] query for error text or related code- [ ] Identify the suspect function from returned processes- [ ] context to see callers and callees- [ ] Trace execution flow via process resource if applicable- [ ] cypher for custom call chain traces if needed- [ ] Read source files to confirm root cause- [ ] State the repository and index freshness with the diagnosis

Debugging Patterns

Symptom	GitNexus Approach
Error message	`query` for error text → `context` on throw sites
Wrong return value	`context` on the function → trace callees for data flow
Intermittent failure	`context` → look for external calls, async deps
Performance issue	`context` → find symbols with many callers (hot paths)
Recent regression	`detect_changes` to see what your changes affect — pass `worktree` for a linked worktree
"How does A reach B?"	`trace` between the two symbols — shortest call chain in one call

Tools

query — find code related to error:

query({search_query: "payment validation error", repo: "my-app"})→ Processes: CheckoutFlow, ErrorHandling→ Symbols: validatePayment, handlePaymentError, PaymentException

query({search_query: "payment validation error", repo: "my-app"})→ Processes: CheckoutFlow, ErrorHandling→ Symbols: validatePayment, handlePaymentError, PaymentException

context — full context for a suspect:

context({name: "validatePayment", repo: "my-app"})→ Incoming calls: processCheckout, webhookHandler→ Outgoing calls: verifyCard, fetchRates (external API!)→ Processes: CheckoutFlow (step 3/7)

context({name: "validatePayment", repo: "my-app"})→ Incoming calls: processCheckout, webhookHandler→ Outgoing calls: verifyCard, fetchRates (external API!)→ Processes: CheckoutFlow (step 3/7)

cypher — custom call chain traces. Pass repo alongside the statement; the Cypher text itself names no repository, so the result is unattributable without it:

cypher

MATCH path = (a)-[:CodeRelation {type: 'CALLS'}*1..2]->(b:Function {name: "validatePayment"})RETURN [n IN nodes(path) | n.name] AS chain

MATCH path = (a)-[:CodeRelation {type: 'CALLS'}*1..2]->(b:Function {name: "validatePayment"})RETURN [n IN nodes(path) | n.name] AS chain

trace — shortest call chain between two symbols ("how does A reach B?"), one call instead of chaining context hops:

trace({ from: "processCheckout", to: "fetchRates", repo: "my-app" })→ status: ok, hopCount: 3→ hops: processCheckout → validatePayment → verifyCard → fetchRates→ edges: CALLS (1.0), CALLS (0.95), CALLS (1.0)

trace({ from: "processCheckout", to: "fetchRates", repo: "my-app" })→ status: ok, hopCount: 3→ hops: processCheckout → validatePayment → verifyCard → fetchRates→ edges: CALLS (1.0), CALLS (0.95), CALLS (1.0)

When no path exists, trace reports the furthest reachable node — exactly where the chain breaks (dynamic dispatch, reflection, or an external boundary).

Example: "Payment endpoint returns 500 intermittently"

0. list_repos {}   → total: 2 (my-app, billing-api) — bind my-app explicitly on every call
1. query({search_query: "payment error handling", repo: "my-app"})   → Processes: CheckoutFlow, ErrorHandling   → Symbols: validatePayment, handlePaymentError
2. context({name: "validatePayment", repo: "my-app"})   → Outgoing calls: verifyCard, fetchRates (external API!)
3. READ gitnexus://repo/my-app/process/CheckoutFlow   → Step 3: validatePayment → calls fetchRates (external)
4. Root cause: fetchRates calls external API without proper timeout   Repository: my-app  Index: current

0. list_repos {}   → total: 2 (my-app, billing-api) — bind my-app explicitly on every call
1. query({search_query: "payment error handling", repo: "my-app"})   → Processes: CheckoutFlow, ErrorHandling   → Symbols: validatePayment, handlePaymentError
2. context({name: "validatePayment", repo: "my-app"})   → Outgoing calls: verifyCard, fetchRates (external API!)
3. READ gitnexus://repo/my-app/process/CheckoutFlow   → Step 3: validatePayment → calls fetchRates (external)
4. Root cause: fetchRates calls external API without proper timeout   Repository: my-app  Index: current

With a single indexed repository, step 0 returns total: 1 and the repo argument drops out of every call above.

来源与署名

来源：abhigyanpatwari/GitNexus位于gitnexus-cursor-integration/skills/gitnexus-debugging提交50aa4be

许可证：无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架

Gitnexus Debugging

Debugging with GitNexus

When to Use

Bind the repository first

Workflow

Checklist

Debugging Patterns

Tools

Example: "Payment endpoint returns 500 intermittently"

来源与署名

更多来自 abhigyanpatwari/GitNexus 的技能

Gitnexus Impact Analysis

Gitnexus Refactoring

Gitnexus Guide

Gitnexus Refactoring

Gitnexus Exploring

Gitnexus Exploring

更多Software Development技能

Playground

M5 Onboard

Cardputer Buddy

Web Design Guidelines

Vercel React Native Skills

Vercel React Best Practices