القائمة
Trace bugs through call chains using knowledge graph
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when the user needs to run OntoIndex CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"
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"
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"
Use when the user asks about OntoIndex itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What OntoIndex tools are available?", "How do I use OntoIndex?"
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"
Use when the user wants to review a pull request, understand what a PR changes, assess risk of merging, or check for missing test coverage. Examples: "Review this PR", "What does PR #42 change?", "Is this PR safe to merge?"
| name | ontoindex-debugging |
| description | Trace bugs through call chains using knowledge graph |
1. ontoindex_query({query: "<error or symptom>"}) → Find related execution flows
2. ontoindex_context({name: "<suspect>"}) → See callers/callees/processes
3. READ ontoindex://repo/{name}/process/{name} → Trace execution flow
4. ontoindex_cypher({query: "MATCH path..."}) → Custom traces if needed
If "Index is stale" → run
npx ontoindex analyzein terminal.
- [ ] Understand the symptom (error message, unexpected behavior)
- [ ] ontoindex_query for error text or related code
- [ ] Identify the suspect function from returned processes
- [ ] ontoindex_context to see callers and callees
- [ ] Trace execution flow via process resource if applicable
- [ ] ontoindex_cypher for custom call chain traces if needed
- [ ] Read source files to confirm root cause
| Symptom | OntoIndex Approach |
|---|---|
| Error message | ontoindex_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 |
ontoindex_query — find code related to error:
ontoindex_query({query: "payment validation error"})
→ Processes: CheckoutFlow, ErrorHandling
→ Symbols: validatePayment, handlePaymentError, PaymentException
ontoindex_context — full context for a suspect:
ontoindex_context({name: "validatePayment"})
→ Incoming calls: processCheckout, webhookHandler
→ Outgoing calls: verifyCard, fetchRates (external API!)
→ Processes: CheckoutFlow (step 3/7)
ontoindex_cypher — custom call chain traces:
MATCH path = (a)-[:CodeRelation {type: 'CALLS'}*1..2]->(b:Function {name: "validatePayment"})
RETURN [n IN nodes(path) | n.name] AS chain
1. ontoindex_query({query: "payment error handling"})
→ Processes: CheckoutFlow, ErrorHandling
→ Symbols: validatePayment, handlePaymentError
2. ontoindex_context({name: "validatePayment"})
→ Outgoing calls: verifyCard, fetchRates (external API!)
3. READ ontoindex://repo/my-app/process/CheckoutFlow
→ Step 3: validatePayment → calls fetchRates (external)
4. Root cause: fetchRates calls external API without proper timeout