1 comments

  • rs54583710 hours ago
    Git diffs are great for humans scanning line noise. But agents need to understand changes: &quot;added function X&quot;, &quot;renamed symbol Y&quot;, &quot;moved block Z&quot;.<p>sem computes semantic diffs on top of your Git repo—no repo rewrite needed.<p>Repo: <a href="https:&#x2F;&#x2F;github.com&#x2F;Ataraxy-Labs&#x2F;sem" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;Ataraxy-Labs&#x2F;sem</a><p>Key ideas:<p>Parses code to AST, computes tree‑edit ops (add&#x2F;remove&#x2F;move&#x2F;change).<p>Outputs human‑&#x2F;agent‑readable patches: &quot;diff_sem&quot; shows intent, not whitespace churn.<p>Applies deterministically via git apply --sem—survives formatting shifts or unrelated edits.<p>Use cases popping up:<p>Agent codemods: output semantic patches instead of brittle hunks.<p>Review tools: &quot;explain this PR as semantic changes&quot;.<p>Stacked diffs &#x2F; Graphite: semantic base for stacks.<p>Bulk refactors: apply &quot;rename all X to Y&quot; across noisy repos.