From a4a231cd1f5251549df36b8b5c60b9448a523869 Mon Sep 17 00:00:00 2001 From: Sarwagya Singh Date: Tue, 14 Jul 2026 03:08:36 +0200 Subject: [PATCH] Add Ontoly Software Graph skill --- .claude-plugin/marketplace.json | 18 +++++++++++++ README.md | 1 + skills/ontoly-software-graph/README.md | 24 +++++++++++++++++ skills/ontoly-software-graph/SKILL.md | 36 ++++++++++++++++++++++++++ 4 files changed, 79 insertions(+) create mode 100644 skills/ontoly-software-graph/README.md create mode 100644 skills/ontoly-software-graph/SKILL.md diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.json index 28a8124..8d9f4bb 100644 --- a/.claude-plugin/marketplace.json +++ b/.claude-plugin/marketplace.json @@ -59,6 +59,24 @@ "perplexity" ] }, + { + "name": "ontoly-software-graph", + "description": "Use Ontoly's deterministic Software Graph and MCP capabilities for architecture review, request tracing, dependency analysis, and impact analysis.", + "source": "./dist/plugins/ontoly-software-graph", + "strict": false, + "skills": [ + "./skills/ontoly-software-graph" + ], + "category": "development", + "keywords": [ + "architecture", + "software-graph", + "mcp", + "dependencies", + "impact-analysis", + "ontoly" + ] + }, { "name": "agent-md-refactor", "description": "Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.", diff --git a/README.md b/README.md index dd457d8..7620b56 100644 --- a/README.md +++ b/README.md @@ -120,6 +120,7 @@ Add skills to project knowledge or paste SKILL.md contents into the conversation | 🛠️ Development | [database-schema-designer](skills/database-schema-designer/README.md) | Design robust database schemas | | 🛠️ Development | [dependency-updater](skills/dependency-updater/README.md) | Smart dependency management | | 🛠️ Development | [naming-analyzer](skills/naming-analyzer/README.md) | Suggest better variable/function names | +| 🛠️ Development | [ontoly-software-graph](skills/ontoly-software-graph/README.md) | Graph-backed architecture, request tracing, dependency, and impact analysis | | 🛠️ Development | [lesson-learned](skills/lesson-learned/README.md) | Extract SE lessons from recent code changes | | 🛠️ Development | [reducing-entropy](skills/reducing-entropy/README.md) | Minimize codebase size | | 🛠️ Development | [session-handoff](skills/session-handoff/README.md) | Seamless AI session transfers | diff --git a/skills/ontoly-software-graph/README.md b/skills/ontoly-software-graph/README.md new file mode 100644 index 0000000..87e4e52 --- /dev/null +++ b/skills/ontoly-software-graph/README.md @@ -0,0 +1,24 @@ +# Ontoly Software Graph + +Graph-backed architecture, request tracing, dependency, and impact analysis using Ontoly's deterministic Software Graph and MCP capabilities. + +## Use Cases + +- Explain a repository's architecture from graph evidence. +- Trace a route or request flow through controllers, services, repositories, and packages. +- Find dependencies, consumers, and impact radius before refactors. +- Review graph diagnostics, trust, framework detection, and semantic coverage. + +## Example Prompts + +```text +Use Ontoly to explain this repository's architecture. +``` + +```text +Use Ontoly to trace the login route through controllers, services, and repositories. +``` + +```text +Use Ontoly to find what depends on UserRepository and what breaks if it changes. +``` diff --git a/skills/ontoly-software-graph/SKILL.md b/skills/ontoly-software-graph/SKILL.md new file mode 100644 index 0000000..e2353f2 --- /dev/null +++ b/skills/ontoly-software-graph/SKILL.md @@ -0,0 +1,36 @@ +--- +name: ontoly-software-graph +description: Use Ontoly's deterministic Software Graph and MCP capabilities for architecture review, request tracing, dependency analysis, and impact analysis. +--- + +# Ontoly Software Graph + +Use Ontoly when an agent needs graph-backed software understanding before searching repository files directly. + +## When to Use + +- Explain repository architecture, modules, packages, services, routes, controllers, or ownership. +- 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 unresolved imports, circular dependencies, dead code, configuration usage, environment variables, or graph diagnostics. + +## Workflow + +1. Check for Ontoly artifacts such as `.ontoly/`, `SoftwareGraph.json`, diagnostics, validation output, or MCP configuration. +2. If the graph is missing and local graph output is acceptable, run `ontoly build .`. +3. Review diagnostics, trust, semantic coverage, framework detection, graph hash, and validation status before making claims. +4. Prefer Ontoly CLI or MCP capabilities for architecture summaries, request tracing, dependency analysis, configuration lookup, framework reports, and impact analysis. +5. Inspect source files only when Ontoly cannot answer, the graph is incomplete, or the user asks for source-level verification. + +## Output + +- Cite graph nodes, edges, packages, routes, diagnostics, or query outputs when available. +- Separate measured graph facts from inference. +- Include confidence based on graph evidence and diagnostics. +- Explain any fallback source inspection and why it was needed. + +## Guardrails + +- Do not invent relationships that are not present in the graph. +- Treat unresolved imports, low trust, missing framework detection, and validation failures as limitations. +- Rebuild the graph after meaningful repository changes before answering current-state questions.