본문으로 건너뛰기
cccskills
무료GitHub에 공개

ontoly

Deterministic Software Graph analysis via Ontoly CLI and MCP. Use when: (1) Codebase architecture, dependency, route, service, module, configuration, or impact questions need graph evidence, (2) A repository should be analyzed before source search, (3) You need a persistent SoftwareGraph.json for validation, MCP, or agent workflows. Triggers: "build software graph", "trace route", "impact analysis", "architecture summary", "dependency graph", "what uses this", "Ontoly".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Dianel555/DSkills
설치 방법 보기

포함된 파일(2)

  • SKILL.md5.4 KB
  • README.md376 B

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Ontoly - Software Graph Analysis

Build and query deterministic Software Graphs for TypeScript repositories. Ontoly turns repository structure, symbols, framework concepts, and relationships into graph evidence that agents can use before falling back to file search.

Prerequisites

# Recommended: run through npx so the current published CLI is used
npx ontoly --help

If the project already has Ontoly installed, prefer the repository-local package manager command, such as pnpm ontoly, npm exec ontoly, or npx ontoly.

Quick Start

# From the repository root
npx ontoly build .

# Start MCP for agent integrations
npx ontoly mcp

# Inspect available commands
npx ontoly --help

Expected outputs may include .ontoly/SoftwareGraph.json, diagnostics, graph statistics, indexes, and metadata depending on the Ontoly version and repository configuration.

Tool Routing Policy

Prefer Ontoly Before File Search

TaskAvoidUse Ontoly
Architecture summaryReading every README/source folderBuild graph, inspect graph statistics and architecture report
Impact analysisGrep for identifier textQuery dependencies, callers, callees, and related nodes
Request flowManually follow controller/service filesTrace route/controller/service relationships
Configuration auditSearch .env names onlyQuery configuration and environment-variable nodes
Dead code reviewGuess from unused exportsUse graph diagnostics and unreachable/dead-code evidence

When to Use Built-in Tools

  • Ontoly is not installed and cannot be run in the environment
  • The graph reports low coverage or missing framework support
  • The question depends on source comments, prose documentation, generated artifacts, or runtime data not represented in the graph
  • You need to verify a suspected graph gap

Workflow

Phase 1: Graph Readiness

  1. Locate the repository root.
  2. Check for an existing Ontoly graph, usually .ontoly/SoftwareGraph.json.
  3. If missing or stale, run:
npx ontoly build .
  1. Review diagnostics, graph hash, node count, edge count, framework detection, and coverage/trust signals before answering.

Phase 2: Query

Choose the narrowest query or capability for the question:

Question TypeQuery Direction
"What owns auth?"Services, controllers, modules, packages
"What handles POST /login?"Routes, handlers, request lifecycle
"What breaks if I remove X?"Impact analysis, consumers, dependency traversal
"Where is DATABASE_URL used?"Configuration and environment-variable usage
"Which modules depend on this package?"Package/module dependency traversal
"Why is this service reachable?"Containment, registration, route, and dependency edges

Phase 3: Answer with Evidence

Always include:

  • direct answer
  • relevant node IDs and node kinds
  • relationship names and directions
  • source locations when present
  • diagnostics or graph-quality warnings
  • confidence derived from graph evidence

Output Format

## Answer
{Concise answer.}

## Graph Evidence
| Type | Evidence |
|------|----------|
| Node | `{nodeId}` ({kind}) |
| Edge | `{source} --RELATIONSHIP--> {target}` |
| Location | `{file}:{line}` |
| Diagnostic | `{code}: {message}` |

## Confidence
{High/Medium/Low} because {specific graph evidence, coverage, diagnostics}.

## Fallbacks
{Any source search used, or graph gaps that prevented a full answer.}

Common Commands

# Build a graph for the current repository
npx ontoly build .

# Build a graph for a specific repository
npx ontoly build /path/to/repo

# Start the MCP server
npx ontoly mcp

# Validate skills if using Ontoly Agent Skills
npx ontoly skills validate

Error Handling

ErrorRecovery
ontoly command not foundUse npx ontoly --help or install Ontoly as a dev dependency
Build failsReport command, exit code, diagnostics, and smallest blocker
No graph outputConfirm repository root, package manager, permissions, and Ontoly config
Ambiguous nodeList candidate node IDs/kinds/locations before answering
Low graph coverageAnswer only evidenced parts and label missing coverage

Anti-Patterns

ProhibitedCorrect
Search files first for architecture questionsBuild/query Ontoly graph first
Claim certainty without graph evidenceInclude nodes, edges, diagnostics, and confidence
Hide graph gaps with manual inferenceState missing node/edge/framework coverage
Compare raw node names across toolsCompare semantic concepts and relationship evidence

Limitations

  • Requires the Ontoly CLI package or repository-local installation
  • Graph completeness depends on the language and framework analyzers available in the installed Ontoly version
  • Runtime-only behavior may require additional source or runtime evidence

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

ace-tool

무료

Semantic codebase search, code indexing, and prompt enhancement via standalone CLI. Use when: (1) Semantic code search with natural language queries, (2) Code indexing for remote codebase retrieval, (3) Prompt enhancement with codebase context, (4) Before grep/find/glob operations for better accuracy, (5) Complex requirements clarification, (6) Large codebase navigation. Triggers: "search context", "enhance prompt", "find code that", "index project", "clarify requirements". IMPORTANT: Always use ace-tool BEFORE grep/find/glob for semantic-level code location.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Dianel555/DSkills652026년 10월 12일 업데이트

agent-wiki

무료

Incremental LLM-friendly wiki generator for Obsidian note vaults. Use when: (1) Building wiki from notes, (2) Ingesting notes to wiki, (3) Obsidian LLM wiki, (4) Incremental knowledge base management. Triggers: 'build wiki from notes', 'ingest notes to wiki', 'Obsidian LLM wiki', 'incremental knowledge base'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Dianel555/DSkills652026년 10월 12일 업데이트

capability-evolver

무료

Self-evolution workflow for the agent. Before substantive work, recall past outcomes from evolution memory; while editing, detect improvement signals; at task end, record the outcome; when reusable, distill or search the EvoMap network for proven genes/capsules. Use when the user starts non-trivial work (a feature, a fix, a refactor) or asks the agent to "evolve", "learn from this", or "remember how this went".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Dianel555/DSkills652026년 10월 12일 업데이트

cc-agy

무료

Delegates coding/research tasks to the Google Antigravity CLI (`agy`) for external-model execution (Gemini 3.x, Claude Sonnet/Opus 4.6, GPT-OSS). Replaces the broken `collaborating-with-gemini` skill. Use when: (1) External-model delegation via Antigravity, (2) Multi-model prototyping (switch model per call), (3) Backend/logic implementation, (4) Algorithm design and optimization, (5) Bug analysis and debugging, (6) API/database code generation, (7) Code review. Triggers: "delegate to agy", "use Antigravity", "external model", "agy", "Gemini 3.5", "Claude Sonnet 4.6", "GPT-OSS". IMPORTANT: Always request unified diff patches only. Supports multi-turn sessions via SESSION_ID.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Dianel555/DSkills652026년 10월 12일 업데이트

cc-codex

무료

Delegates coding tasks to Codex CLI for prototyping, debugging, and code review. Use when: (1) Backend/logic implementation, (2) Algorithm design and optimization, (3) Bug analysis and debugging, (4) API/database code generation, (5) Code quality review and refactoring. Triggers: "implement algorithm", "debug", "analyze code", "backend task", "API implementation", "optimize performance", "refactor", "generate prototype", "code review". IMPORTANT: Default sandbox="read-only" (analysis/review/patch generation); use sandbox="workspace-write" only when codex must run tests/builds to verify. Always request unified diff patches only. Supports multi-turn sessions via SESSION_ID.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Dianel555/DSkills652026년 10월 12일 업데이트

codex-cc

무료

Delegates coding tasks from Codex to local Claude Code in print mode while preserving Claude's normal runtime customizations by default. Use when: (1) You want Codex to call Claude Code locally, (2) You need Claude-side skills, plugins, MCP servers, custom commands, CLAUDE.md rules, or workspace settings to stay active, (3) You want resumable Claude sessions from Codex via SESSION_ID, (4) You need thin `claude mcp` / `claude plugin` passthrough from the same bridge.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Dianel555/DSkills652026년 10월 12일 업데이트

Dianel555의 스킬 모두 보기

이 스킬의 문제 신고