メニュー
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?"
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 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?"
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file"
| name | ontoindex-guide |
| description | 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?" |
Quick reference for all OntoIndex MCP tools, resources, and the knowledge graph schema.
For any task involving code understanding, debugging, impact analysis, or refactoring:
ontoindex://repo/{name}/context — codebase overview + check index freshnessIf step 1 warns the index is stale, run
npx ontoindex analyzein the terminal first.
| Task | Skill to read |
|---|---|
| Understand architecture / "How does X work?" | ontoindex-exploring |
| Blast radius / "What breaks if I change X?" | ontoindex-impact-analysis |
| Trace bugs / "Why is X failing?" | ontoindex-debugging |
| Rename / extract / split / refactor | ontoindex-refactoring |
| Tools, resources, schema reference | ontoindex-guide (this file) |
| Index, status, clean, wiki CLI commands | ontoindex-cli |
| Tool | What it gives you |
|---|---|
query | Process-grouped code intelligence — execution flows related to a concept |
context | 360-degree symbol view — categorized refs, processes it participates in |
impact | Symbol blast radius — what breaks at depth 1/2/3 with confidence |
detect_changes | Git-diff impact — what do your current changes affect |
rename | Multi-file coordinated rename with confidence-tagged edits |
cypher | Raw graph queries (read ontoindex://repo/{name}/schema first) |
list_repos | Discover indexed repos |
Lightweight reads (~100-500 tokens) for navigation:
| Resource | Content |
|---|---|
ontoindex://repo/{name}/context | Stats, staleness check |
ontoindex://repo/{name}/clusters | All functional areas with cohesion scores |
ontoindex://repo/{name}/cluster/{clusterName} | Area members |
ontoindex://repo/{name}/processes | All execution flows |
ontoindex://repo/{name}/process/{processName} | Step-by-step trace |
ontoindex://repo/{name}/schema | Graph schema for Cypher |
Nodes: File, Function, Class, Interface, Method, Community, Process Edges (via CodeRelation.type): CALLS, IMPORTS, EXTENDS, IMPLEMENTS, DEFINES, MEMBER_OF, STEP_IN_PROCESS
MATCH (caller)-[:CodeRelation {type: 'CALLS'}]->(f:Function {name: "myFunc"})
RETURN caller.name, caller.filePath