skills.rest
semantica-agi
semantica-agiOFFICIAL
Explore all skills by this author →
Website𝕏@BuildSemanticaGitHub

change

Compute diffs between Semantica knowledge graph snapshots and retrieve node histories.

3.0k|350|Updated Jun 25, 2025
Search Tags:#audit#provenance#diff#temporal#graph#change-tracking
One-click install
npx skills add https://github.com/semantica-agi/semantica --skill change-semantica-agi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: change
Source: https://github.com/semantica-agi/semantica/tree/main/plugins/skills/change
Command: npx skills add https://github.com/semantica-agi/semantica --skill change-semantica-agi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track and inspect changes, diffs, and temporal updates to knowledge graphs to maintain an auditable trail of data evolution.

Core Features & Use Cases

  • Compute graph diffs between snapshots to identify added/removed nodes and edges and attribute changes.
  • Show change history for a node or relationship over time with summaries.
  • Support provenance and auditability with summaries of impact and integration with the Semantica context graph.

Quick Start

Inspect diffs between snapshots and review node histories to understand how your knowledge graph evolved over time.

Frequently Asked Questions about change

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

FAQPage Schema
How do I track changes in a knowledge graph over time?▼

Tracking changes in a knowledge graph involves computing diffs between snapshots to identify added or removed nodes, edges, and attribute changes. This maintains an auditable trail of data evolution for temporal updates and provenance auditing.

What is graph provenance auditing and when do I need it?▼

Graph provenance auditing is the process of inspecting temporal updates and node histories to maintain an auditable trail of data evolution. You need it to verify data integrity, assess change impact, and understand how relationships evolved across graph data stores.

Can I compute a diff between two graph snapshots to see what was removed?▼

Yes, you can compute diffs between graph snapshots to identify added or removed nodes and edges, as well as attribute changes. This allows you to see exactly what was removed or modified during temporal updates.

How do I retrieve the change history for a specific node in a graph database?▼

Retrieving the change history for a specific node involves querying temporal updates to show its evolution over time with summaries. This tracks the node's relationship and attribute changes across different graph snapshots.

What is the best way to assess the impact of temporal updates on graph data stores?▼

The best way to assess the impact of temporal updates is by summarizing change impact using a ChangeTracker and ContextGraph. This approach evaluates graph diffs and node histories to understand the full scope of data evolution.

Does this change tracking approach work without external dependencies?▼

Yes, this change tracking approach works without external dependencies, relying on the internal ChangeTracker and ContextGraph components. It directly computes graph diffs and provenance summaries within the Semantica environment.

Related Skills

Explore More Data & Analytics Skills→
optaveoptave
86

titan-reset

Remove Titan artifacts and restore the codebase to its pre-Titan baseline.

Official
Advanced
abnejLLCabnejLLC

so-what-translation

Translate GRC reports and technical findings into executive summaries for decision-making.

Community
Intermediate
qiubohongqiubohong
5

gitnexus-guide

Guide GitNexus tool usage for code analysis and refactoring tasks.

Community
Basic
maltemdmaltemd

diffing-and-versioning-context-packs

Compare context pack versions and generate semantic diffs with changelogs.

Community
Intermediate