Use Ontoly's deterministic Software Graph and MCP capabilities for architecture review, request tracing, dependency analysis, configuration lookup, and impact analysis before falling back to source-fi
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add anbeime/skill --skill ontoly-software-graph -a cursor -y
Use Ontoly's deterministic Software Graph and MCP capabilities for architecture review, request tracing, dependency analysis, configuration lookup, and impact analysis before falling back to source-file search.
Use Ontoly's deterministic Software Graph and MCP capabilities for architecture review, request tracing, dependency analysis, configuration lookup, and impact analysis before falling back to source-file search.
Use this skill when a coding agent needs evidence-backed software understanding from an Ontoly graph before searching repository files directly.
Check whether an Ontoly graph already exists by looking for .ontoly/, SoftwareGraph.json, diagnostics.json, validation reports, or an Ontoly MCP configuration.
If no graph exists and the user permits local analysis, run:
ontoly build .
Inspect graph health before answering: diagnostics, graph hash, semantic coverage, trust or quality score, framework detection, and generation timestamp.
Prefer Ontoly CLI or MCP capabilities for graph questions instead of scanning source files first.
Use repository search only when Ontoly cannot answer, the graph is stale, the graph is incomplete, or the user explicitly asks for source-level verification.
Always cite graph evidence in the answer: node IDs, edge types, file paths, source locations, diagnostics, or framework analyzer output.
State confidence from graph evidence. Do not guess confidence.
ExplainArchitecture for repository and package topologyFindDependencies for dependency trees and direct consumersImpactAnalysis for refactor blast radiusTraceExecution for request, route, and call-flow tracingFindConfigurationUsage for configuration and environment variable usageFrameworkReport for detected framework concepts such as modules, controllers, providers, and routesFindDeadCode for unreachable or unused graph regionsWhen answering, include:
Example:
AuthController handles authentication.
Evidence:
- node: class:src/auth/auth.controller.ts:AuthController
- route edges: HANDLES POST /login, POST /logout
- dependency edges: USES AuthService, JwtService
Confidence: high, because the graph has controller, route, and dependency edges with source locations.
NOT_FOUND with the closest graph evidence instead of inventing an answer.