ontology

Query and manage project ontology entities and relationships via CLI.

8|2|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/seokan-jeong/team-shinchan --skill ontology-seokan-jeong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ontology
Source: https://github.com/seokan-jeong/team-shinchan/tree/main/skills/ontology
Command: npx skills add https://github.com/seokan-jeong/team-shinchan --skill ontology-seokan-jeong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The ontology skill enables teams to discover, inspect, and manage project-level entities and their relationships so knowledge is organized, searchable, and reviewable across sessions.

Core Features & Use Cases

  • Ontology Summary & Metrics: Generate counts for entities, relations, and type distributions to understand coverage and hotspots.
  • Search and Query: Find entities by name or type and inspect their relations to support architecture reviews and impact analysis.
  • Edit and Sync: Add or remove entities, trigger full project scans to merge discovered concepts, and regenerate KB summaries; generate Mermaid diagrams for module dependency or domain maps.
  • Use Case: During a release planning meeting, scan the repository, query payment-related components, visualize their neighborhood, and add a decision entity documenting the chosen API approach.

Quick Start

Use the ontology skill to show a project summary and visualize the most connected entities.

Frequently Asked Questions about ontology

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

FAQPage Schema
How do I visualize project architecture and component dependencies?

To visualize project architecture and component dependencies, you can scan your codebase to discover entities and generate Mermaid diagrams. This surfaces module dependency graphs and domain maps for architecture reviews and planning sessions.

What is a project ontology and when do I need to build one?

A project ontology organizes software components, decisions, and dependency relationships into a searchable knowledge graph. You need to build one when you want to discover, inspect, and manage project-level entities so knowledge stays structured across planning sessions.

How do I query entities and relationships in a codebase for impact analysis?

You can query entities and relationships in a codebase by searching for specific component names or types. The ontology engine inspects their relations and provides summary metrics to support impact analysis during architecture reviews.

Can I generate a knowledge graph from existing documentation and code?

Yes, you can generate a knowledge graph from existing documentation and code by running a full project scan. This merges discovered concepts into the knowledge base, allowing you to add or remove entities and regenerate summary metrics.

What's the best way to document architectural decisions during a release planning meeting?

The best way to document architectural decisions during release planning is to scan the repository, query the affected components, and add a decision entity to the ontology. This captures the chosen API approach within the project knowledge graph.

How do I identify dependency hotspots and coverage gaps in my project?

To identify dependency hotspots and coverage gaps, generate ontology summary metrics that provide counts for entities, relations, and type distributions. This helps you understand coverage and pinpoint highly connected components.