Ontoly Software Graph

Use this skill when a coding agent needs evidence-backed software understanding from an Ontoly graph before searching repository files directly.

When to Use

• Explaining a repository architecture
• Tracing a request, route, controller, service, or dependency path
• Finding owners of services, modules, routes, configuration, or environment variables
• Reviewing dependency impact before a refactor
• Auditing dead code, cycles, unresolved imports, graph quality, or semantic coverage
• Preparing documentation, onboarding notes, or architecture review from graph evidence

Required Workflow

1. Check whether an Ontoly graph already exists by looking for .ontoly/, SoftwareGraph.json, diagnostics.json, validation reports, or an Ontoly MCP configuration.
2. If no graph exists and the user permits local analysis, run: