ontoly
SolidDeterministic Software Graph analysis via Ontoly CLI and MCP. Use when: (1) Codebase architecture, dependency, route, service, module, configuration, or impact questions need graph evidence, (2) A repository should be analyzed before source search, (3) You need a persistent SoftwareGraph.json for validation, MCP, or agent workflows. Triggers: "build software graph", "trace route", "impact analysis", "architecture summary", "dependency graph", "what uses this", "Ontoly".
Install
Quality Score: 84/100
Skill Content
Details
- Author
- Dianel555
- Repository
- Dianel555/DSkills
- Created
- 7 months ago
- Last Updated
- 2 days ago
- Language
- Python
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
graphify
Use for tracing how code connects across files - "how does A reach B", "is there a route from X to Y", "what sits between these two modules", "what breaks if I change X" - and for orienting in an unfamiliar or large repo. Builds a queryable call/import graph once (graphify update), then answers with graphify path, affected, explain and query against that graph. Do NOT use when one bounded grep or one Read already answers the question, or on a repo small enough to read into context. Maps CODE structure, not agent workflows.
codegraph
Query a repository's CodeGraph index (MCP tools or the codegraph CLI) instead of broad grep and file reading. Use when locating the code relevant to a task or ticket, understanding an unfamiliar codebase, finding a symbol's callers or callees, estimating a change's blast radius, tracing dependencies, or finding tests related to a change.
graph-explorer
Navigate the graph_os knowledge graph before editing load-bearing code. Use when tracing dependencies, planning a rename, auditing API surface, or answering "what breaks if I change this?". Pairs with codebase-explorer — graph-explorer wins for symbol-precise queries, codebase-explorer wins for conceptual code-reading.