domains / families / software-engineering / ontoly-software-graph

ontoly-software-graph

combined

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 server for codebase architecture, request tracing, dependency analysis, and impact analysis.

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
• Use when the user asks for repository architecture, module ownership, or onboarding help.
• Use when tracing a request, route, controller, service, provider, dependency, or call chain.

When not to use

• Ontoly does not replace compiler, test, or runtime validation.
• Graph quality depends on the Ontoly version, supported language frontend, repository setup, and diagnostics.
• Missing or partial framework detection lowers confidence for framework-specific answers.
• Do not claim a relationship exists unless it is present in the graph or clearly labeled as an inference.
• Stop and ask for clarification if the repository path, target graph, or requested analysis scope is ambiguous.

Skill page

Conflict

The three copies describe the same core workflow (check for graph, build if missing, check diagnostics, use Ontoly, fall back to source), but each contains material steps or constraints the others lack. The anbeime copy adds a specific 'Answer Shape' and 'Fallback Rules' (e.g., NOT_FOUND handling, disambiguation). The sickn33 copy adds a 'Security & Safety' section, specific CLI verification commands (`ontoly --help`, `find`), and a step to start the MCP server (`ontoly mcp`). The davepoon copy is the most concise but lacks the specific capability names and safety constraints found in the others. Crowning one would hide the specific operational details (like security notes or specific MCP commands) present in the others.