ontoly-software-graph

Query a deterministic Software Graph for TypeScript codebase architecture, tracing, and impact analysis.

3.4k|487|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/davepoon/buildwithclaude --skill ontoly-software-graph
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ontoly-software-graph
Source: https://github.com/davepoon/buildwithclaude/tree/main/plugins/all-skills/skills/ontoly-software-graph
Command: npx skills add https://github.com/davepoon/buildwithclaude --skill ontoly-software-graph

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Understanding a large TypeScript codebase by reading source files one by one is slow and error-prone. This Skill directs the agent to Ontoly's deterministic Software Graph so architecture questions, request tracing, and impact analysis are answered from verified graph data instead of guesswork.

Core Features & Use Cases

  • Architecture Analysis: Explain repository structure, module ownership, services, routes, packages, and dependencies from graph nodes and edges.
  • Request & Dependency Tracing: Trace a request from route to controller, service, and repository, or follow call chains and dependency paths.
  • Impact Analysis: Estimate what breaks when renaming, removing, or refactoring a symbol, module, package, route, or service.
  • Graph Diagnostics: Check trust levels, semantic coverage, framework detection, circular imports, dead code, and validation failures before making claims.
  • Use Case: Ask the agent to trace the login flow from route to repository, and it queries the Ontoly graph via CLI or MCP, citing exact nodes and edges rather than inferring relationships from raw source.

Quick Start

Ask the agent to use Ontoly to explain this repository's architecture and trace what depends on a specific module.

Frequently Asked Questions about ontoly-software-graph

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze TypeScript codebase architecture with a software graph?

Build a Software Graph with the ontoly build command, then query it through the Ontoly CLI or MCP capabilities for architecture summaries, module ownership, routes, and dependencies. The graph provides deterministic answers instead of inferred relationships from raw source files.

How to trace a request from route to service in a TypeScript repo?

Use Ontoly's request tracing to follow a route through its controller, service, provider, and repository layers. The skill instructs the agent to cite exact graph nodes and edges for each hop in the call chain.

What is impact analysis for refactoring a module?

Impact analysis identifies every symbol, package, route, or service that depends on code you plan to rename, remove, or refactor. Ontoly answers this from graph dependency edges, showing what breaks before you make the change.

Does Ontoly work if no graph exists in the repository yet?

Yes, the skill checks for an existing graph such as .ontoly/ or SoftwareGraph.json first, and runs ontoly build . to generate one when local graph output is appropriate. Source files are only inspected when the graph is missing or untrusted.

When should I read source files instead of using the software graph?

Inspect source directly when the graph is missing, incomplete, has low trust scores, failed validation, or when you explicitly need source-level verification. Unresolved imports and missing framework detection are treated as answer limitations.