Today marks a personal milestone: I have finally finished a massive, six-month-long refactoring of my other project, gomarklint . After spending half a year staring at Go code structures and AST nodes, I realized something painful. Our current tools are still "dumb" when it comes to understanding the intent of our changes. We are still reviewing code line-by-line, even though we think in structures and logic. That's why I'm excited to announce my next OSS project: gosemdiff . The Problem with Current Solutions (Including AI) We now have AI tools that can summarize Pull Requests for us. They are helpful, but let's be honest: AI summaries are often "vibes-based." An AI might say, "This PR refactors the processing logic," but it can't mathematically guarantee that the logic remains unchanged. AI can hallucinate, overlook edge cases, or fail to distinguish between a variable rename and a subtle logic bug. As engineers, we don't need a "guess." We need proof . Standard git diff treats code as text.…