semantic-diff

Semantic version control => entity-level diffs, blame, and impact analysis on top of git. 28 languages via tree-sitter. Built for coding agents.

Awesome tools that show differences between files and folders.

Community support for SemanticDiff, the programming language aware diff for Visual Studio Code and GitHub.

Semantic, format-aware diff for config & structured-data files (JSON, YAML, TOML, INI, .env, .properties, CSV, XML). See what actually changed — keys and values, not text noise.

SymDiff-Differential-Program-Verifier

Tools for working with KGCL

Experiment about a semantic-based diff tool for Java language.

Understand what changed, not just where.

Semantic config watcher — plain-English diffs, policy packs, CI gates, and webhooks

Repository for ASE 2018 paper, "Datalog-based Scalable Semantic Diffing of Concurrent Programs".

Portable Agent Skill for semantic diff, review prioritization, and merge workflows

A generic, semantic tree-diff algorithm for XML-shaped documents & a frontend for comparing query plans from different database systems

GitHub Action for installing and running sbom-tools — semantic SBOM diff, validation, and quality scoring

Structure-aware Git diff for code review: collapse formatting noise, detect moved code, probable renames, import reorders, and meaningful edits

SemanticDiff is a desktop Git diff explorer that turns repository changes into an interactive, semantic graph.

Semantic YAML Analysis

Git-for-research: a research-native version control system. Content-addressed immutable artifacts, semantic per-type diffing, three-way prose merge, CRDT concurrency, and first-class research provenance. Built for a 13h hackathon.

Comparo: AI-powered legal & contract clause comparison engine with semantic diff highlighting.

Semantic, human-grade diffs for YAML/JSON/HCL configuration files

AuthContract turns institutional rules into developer-usable, testable controls. It connects authoritative rule sources to canonical contracts, CI/CD merge gates, runtime action checks, and reconstructable evidence—so teams can prove not just what an agent did, but which rule authorized it, what version applied, and why execution was allowed.