Menú
Navigate unfamiliar code using OntoIndex knowledge graph
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional 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-exploring |
| description | Navigate unfamiliar code using OntoIndex knowledge graph |
1. READ ontoindex://repos → Discover indexed repos
2. READ ontoindex://repo/{name}/context → Codebase overview, check staleness
3. ontoindex_query({query: "<what you want to understand>"}) → Find related execution flows
4. ontoindex_context({name: "<symbol>"}) → Deep dive on specific symbol
5. READ ontoindex://repo/{name}/process/{name} → Trace full execution flow
If step 2 says "Index is stale" → run
npx ontoindex analyzein terminal.
- [ ] READ ontoindex://repo/{name}/context
- [ ] ontoindex_query for the concept you want to understand
- [ ] Review returned processes (execution flows)
- [ ] ontoindex_context on key symbols for callers/callees
- [ ] READ process resource for full execution traces
- [ ] Read source files for implementation details
| Resource | What you get |
|---|---|
ontoindex://repo/{name}/context | Stats, staleness warning (~150 tokens) |
ontoindex://repo/{name}/clusters | All functional areas with cohesion scores (~300 tokens) |
ontoindex://repo/{name}/cluster/{name} | Area members with file paths (~500 tokens) |
ontoindex://repo/{name}/process/{name} | Step-by-step execution trace (~200 tokens) |
ontoindex_query — find execution flows related to a concept:
ontoindex_query({query: "payment processing"})
→ Processes: CheckoutFlow, RefundFlow, WebhookHandler
→ Symbols grouped by flow with file locations
ontoindex_context — 360-degree view of a symbol:
ontoindex_context({name: "validateUser"})
→ Incoming calls: loginHandler, apiMiddleware
→ Outgoing calls: checkToken, getUserById
→ Processes: LoginFlow (step 2/5), TokenRefresh (step 1/3)
1. READ ontoindex://repo/my-app/context → 918 symbols, 45 processes
2. ontoindex_query({query: "payment processing"})
→ CheckoutFlow: processPayment → validateCard → chargeStripe
→ RefundFlow: initiateRefund → calculateRefund → processRefund
3. ontoindex_context({name: "processPayment"})
→ Incoming: checkoutHandler, webhookHandler
→ Outgoing: validateCard, chargeStripe, saveTransaction
4. Read src/payments/processor.ts for implementation details