ontology-as-code

Plugin ontology-as-code in leduykhuong-daniel/OSS-ontology-as-code-kit. Commands read from the repo's manifest — 1 month ago.

Skills (5)

• digital-twin-intro

  Use when explaining how an operational ontology becomes a digital twin — covers the twinning loop (model + live data + behavior), the 5-level maturity ladder, and how AI agents operate on a twin. Pairs with ontology-as-code-intro.

• ontology-as-code-cicd

  Use when wiring Ontology-as-Code into Git and CI — branching for an ontology, reviewing a schema change as a pull request, the four CI gates (validate PASS / expect-FAIL / codegen smoke / drift), semver for schema evolution, and the codegen pipeline. Trigger whenever the user wants CI, a pipeline, a

• ontology-as-code-intro

  Use when introducing a team to Ontology-as-Code — explains the operational ontology concept, the 6-atom model (object/attribute/link/action/policy/event), how it differs from BI semantic layers, and the first steps to model one entity on LinkML.

• ontology-modeling

  Use when modeling any of the 6 atoms of an ontology/digital twin — ObjectType, AttributeType, LinkType, ActionType, PolicyType, EventType — the semantic-first way. Covers the business questions to ask before listing attributes, links as native slots, kinetic atoms as contracts, and data binding for

• twin-lifecycle

  Use for day-2 operations on a digital twin — adding, modifying, or deprecating a domain with breaking-change discipline, monitoring twin health (binding/freshness, governance ownership, event-stream, drift), and adopting ontology into an existing codebase. Trigger whenever the user wants to evolve,

Slash commands (11)

• /ontology-as-code:README
• /ontology-as-code:adopt

  Adopt Ontology-as-Code into an EXISTING codebase (brownfield) — scan code and docs for candidate entities, links, and policies, then draft 6-atom ontology for review. Use when the user wants to bring ontology/digital-twin into a project that already has code, models, a database, or docs.

• /ontology-as-code:audit

  Audit the health of a digital twin — binding/freshness, governance ownership, event-stream, and drift signals, plus maturity-ladder position. Use when the user wants a health check, audit, or wants to find gaps, drift, unowned objects, or assess how mature/alive their twin is.

• /ontology-as-code:bind

  Wire an ObjectType to its live data source (twinning) via x_data_binding + x_sync_mode, turning a static model into a living digital twin. Use when the user wants to connect, bind, or map an object to real data, set up data binding, or make the model "live".

• /ontology-as-code:ci

  Generate a CI workflow (GitHub Actions) that gates the ontology on every PR — validate PASS, expect-FAIL, and codegen smoke. Use when the user wants to add CI, set up a pipeline, gate, or automated check for their ontology/twin.

• /ontology-as-code:codegen

  Generate code artifacts from the ontology — Pydantic SDK, JSON-Schema, and a Mermaid ER diagram. Use when the user wants to generate, build, or codegen an SDK, models, JSON schema, or an entity-relationship diagram from their ontology/twin.

• /ontology-as-code:evolve

  Evolve a domain safely — add, modify, or deprecate an atom and detect whether the change is breaking. Use when the user wants to add/change/remove a domain concept, rename a field, deprecate something, or asks whether a schema change is a breaking change.

• /ontology-as-code:init

  Scaffold a new digital-twin ontology project (greenfield) — one-atom-per-folder structure + root + CI that validates immediately. Use when the user wants to start, set up, init, or scaffold an ontology/digital-twin on a repo from scratch.

• /ontology-as-code:learn

  Teach Ontology-as-Code from scratch — the 6-atom model, digital twin idea, and the 11-lesson path. Use when someone wants to learn, understand, or get started with ontology-as-code or digital-twin-as-code.

• /ontology-as-code:model

  Model a 6-atom entity — create an ObjectType, ActionType, PolicyType, or EventType from a template. Use when the user wants to add, model, define, or create a domain concept, object, action, policy, rule, or event in their ontology/twin.

• /ontology-as-code:validate

  Validate an ontology schema and (optionally) a data instance against it with LinkML. Use when the user wants to validate, check, verify, or lint their ontology/twin schema or test data against the model.

Subagents (4)

• README
• breaking-change-detector

  Analyzes an ontology schema change and classifies it as breaking or non-breaking, reasoning about downstream impact on data consumers and generated SDKs, then recommends a semver bump. Use when the user changed an ontology schema and asks whether it is a breaking change, or before merging an ontolog

• ontology-adopter

  Brownfield orchestrator — scans an existing codebase and docs, then proposes a candidate 6-atom ontology (ObjectTypes with attributes, Links, and Policy/Action candidates) grounded in the real code and documentation found. Use when adopting ontology-as-code or a digital twin into a project that alre

• twin-health-auditor

  Deep health audit of a digital twin beyond the heuristic script — compares x_data_binding targets to real source schemas (true drift), checks binding freshness, governance ownership, event-stream coverage, and the twin's maturity-ladder position. Use when the user wants a thorough health check or au

Similar plugins