sem

“They at least give a more structured approach to dealing with code than simple text.”

“indispensable for models to make less mistakes for me”

“I'd remove setup/unsetup commands and replace with a note that if you want to use it for git diff”

“incredibly obnoxious that it overrides default git diff”

“This looks really neat, but I see its diff output as complimentary to git”

“A step in the right direction, and interesting in that it layers over existing git”

“The tool looks great! Thanks for sharing.”

“But there are no instructions for how to reverse those actions if you don't like the tool.”

“Your tool is cool. Sell it for what it is. Not for what it's not.”

“I doubt if this actually solves a real problem for humans or agents”

“Okay that is pretty cool. I appreciate this information as a human also.”

“The benchmarks aren't great, they're super specific to sem's output”

“working across multiple languages with a single tool can be quite helpful”

“extracts entities from 30+ languages via tree-sitter and builds a cross-file dependency graph”

“Semantic diffing would pair really well with stacks.”

“The key insight is distinguishing signature changes from body changes.”

“sem does it structurally: parses both sides with tree-sitter, computes structural hashes, walks the real dependency graph”

“sem gives you both. sem diff --verbose shows the full before/after body of each changed entity.”

“It tells you the function changed but not how; you still need line-level diffs.”

“Instead of showing you which syntax nodes changed, it shows you which functions, classes, and methods changed”

“i think that's where version control is going”

“I am not sure if these are ready for prime-time yet.”

“sem already does this. sem graph builds a cross-file entity dependency graph and sem impact tells you”

“that level of understanding is enough to resolve 100% of false conflicts on our benchmarks”

“sem stays on top of git so there's zero migration cost, you keep your existing repo and workflows.”

“purely cosmetic changes like reformatting or renaming a local variable won't show as a diff”

“as it relies on function names and changes therein having a direct mapping to meaning with standard text processing”

“I'm glad someone else already implemented it with support for more languages.”

“knowledge graph matching on top of commits”

“When AI agents are committing hundreds of changes a session, you need to know which functions changed, not which lines”

“Fully deterministic, no llm calls”

“For most application-level C++ it works well, but something like the Linux kernel would be rough.”

“Much less tokens, and much more accurate”

“which does entity-level diffs”

“sem computes semantic diffs on top of your Git repo—no repo rewrite needed.”

“Results: 95.9% accuracy vs 41.5%.”