Agent Skills
› davepoon/buildwithclaude
› ontoly-software-graph
ontoly-software-graph
GitHub提供基于Ontoly软件图的代码库架构理解、请求追踪、依赖分析及影响分析工作流。通过CLI或MCP查询获取确定性图谱信息，辅助进行架构解释、模块所有权确认及重构风险评估，仅在图谱缺失或不信任时查阅源码。
Trigger Scenarios
需要解释仓库架构或模块依赖关系
追踪特定功能（如登录流程）的请求链路
评估符号或模块变更的影响范围
检查循环导入或死代码
Install
npx skills add davepoon/buildwithclaude --skill ontoly-software-graph -g -y
SKILL.md
Frontmatter
{
"name": "ontoly-software-graph",
"license": "MIT",
"category": "development-code",
"description": "Use Ontoly's deterministic Software Graph and MCP server for codebase architecture, request tracing, dependency analysis, and impact analysis."
}
Ontoly Software Graph
Use Ontoly when a coding agent needs graph-backed software understanding before searching source files directly.
Ontoly builds a deterministic Software Graph from a TypeScript repository and exposes it through CLI queries, MCP capabilities, and agent skills. The skill teaches workflow only; Ontoly remains the source of truth.
Workflow
- Check whether an Ontoly graph already exists in the repository, such as
.ontoly/,SoftwareGraph.json, or documented Ontoly scripts. - If the graph is missing and local graph output is appropriate, run
ontoly build .. - Check graph diagnostics, trust, semantic coverage, framework detection, and validation before making architecture claims.
- Prefer Ontoly CLI or MCP capabilities for architecture summaries, request tracing, dependency analysis, configuration lookup, framework reports, and impact analysis.
- Inspect source files only when the graph is missing, incomplete, untrusted for the question, or the user explicitly asks for source-level verification.
Use Cases
- Explain repository architecture, module ownership, services, routes, packages, or dependencies.
- Trace a request, route, controller, service, provider, dependency, or call chain.
- Estimate impact for removing, renaming, or refactoring a symbol, module, package, route, or service.
- Review circular imports, dead code, configuration usage, environment variables, or graph diagnostics.
Evidence Rules
- Separate graph facts from inference.
- Cite exact graph nodes, edges, packages, routes, diagnostics, or query outputs when available.
- Treat unresolved imports, low trust, missing framework detection, and validation failures as answer limitations.
- Do not claim a relationship exists unless Ontoly reports it or the answer labels it as inferred.
Example Prompts
Use Ontoly to explain this repository's architecture.
Use Ontoly to trace the login flow from route to controller, service, and repository.
Use Ontoly to find what depends on UserRepository and what breaks if it changes.
Version History
- b79ed72 Current 2026-07-19 18:36
