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.