git-clash

Forensic Semantic Drift Analyzer for Multi-Agent Repositories

Are you running multiple AI Coding Agents (like Devin, Sweep.dev, or Copilot Workspace) on the same repository? Standard Git was built for humans, not AI.

When two AI agents make concurrent edits to the same file, Git's line-based algorithm often merges them cleanly without raising a conflict. However, if Agent A renamed a function and Agent B wrote new code calling the old function, your code is now logically broken. We call these Phantom Regressions.

git-clash uses the Hivecode ICR Engine (Intent-aware Code Replication) to parse the actual Abstract Syntax Tree (AST) of your code and detect silent semantic breaks that standard Git misses.

Quick Start (No Installation Required)

Audit your repository for Phantom Regressions instantly:

npx git-clash scan

The CLI will scan your recent Git merges, perform an AST-level simulation, and generate a FISSION CRITICAL ANALYSIS REPORT if it detects any semantic drift.

Output

  ┌────────────────────────────────────────────────────────────┐
  │           ⚠  FISSION CRITICAL ANALYSIS REPORT  ⚠           │
  └────────────────────────────────────────────────────────────┘

  Repository scanned:  ./
  Analysis engine:     ICR (Intent-aware Code Replication) v0.1.6

   CRITICAL  1 SILENT SEMANTIC BREAK DETECTED
  Standard Git merged these cleanly. Your CI passed. The code is broken.

  ────────────────────────────────────────────────────────────

The Permanent Fix

git-clash diagnoses the disease, but it doesn't cure it. If your agent fleet is suffering from high Semantic Drift, transition your agents from "Advisory Isolation" to "Pre-Write Admission Control."

Install the Hivecode Pre-Write Daemon to synchronize your agents' ASTs in real-time and prevent Phantom Regressions before they are ever written to disk.

Learn more about the Hivecode Daemon