Opening

A git difftool written in Rust hit 311 points on Hacker News and 862 stars. OmniDiff doesn't just diff code: it handles images, PDFs, archives, fonts, and even mouse cursors, with a median completion time under 100ms. Also today: an AI-interface rescue kit that racked up 6.3k stars in 30 days, built specifically to hunt down purple gradients, "New ✨" badges, and all the other dead giveaways that a human didn't design this. I'll show you how to wire it into Claude Code in a minute. I'm Muyan, this is the Open Source Daily, November 2, 2026.

Today's Picks

1. OmniDiff: a git difftool that understands syntax, and PDFs too

• What it is: The most annoying part of code review is when you only changed indentation or moved a function, yet the diff lights up the whole screen in red and green. OmniDiff is a content-aware difftool written in Rust, doing syntax-aware comparison via tree-sitter ASTs across 25 languages. And not just code: config files, images, PDFs, archives, cursors, and fonts all diff too. The author has been using it as a daily git difftool for months. It's the kind of tool you install and immediately go edit your .gitconfig for.
• Recent buzz: 311 points and 94 comments on Hacker News, 862 stars on GitHub.
• Standout features: First, tree-sitter AST syntax-aware diffing, with the README claiming it handles 99.95% of code changes. Second, the performance targets are written right into the README: median diff under 100ms, 99th percentile under 1000ms, and even C++ files with tens of thousands of lines finish in under 100ms on a 2023 ThinkPad T14s. Third, integration paths are thorough: you can set it as the default with git config diff.tool omnidiff, or hook it straight into git diff and git log -p via GIT_EXTERNAL_DIFF, plus there's support for jj's merge-tools config. There's also --mode json to emit the diff as a single JSON object, and extensions exist for VS Code (including VSCodium, Cursor, and Windsurf via Open VSX) and Neovim.
• Getting started: One line on macOS with brew install ivankovic/omnidiff/omnidiff, or cargo install --locked omnidiff (requires rustc 1.92+ and a C compiler). If you don't want to install anything yet, hit the showcase on the official site for 20 real-world changes with Unix diff and OmniDiff shown side by side.
• How it compares: In the HN thread the author responded directly: delta essentially just colorizes the standard git diff algorithm, while OmniDiff uses a completely different one. Compared to difftastic, which is also syntax-aware, the difference is that difftastic only eats code, while OmniDiff diffs images, PDFs, fonts, and archives too. One caveat worth stating plainly: the license is GNU AGPL v3 or later. Personal use and internal tooling are fine, but talk to legal before bundling it into a customer-facing product.
• Who it's for: Engineers who live in code review and frequently need to compare design files or binary assets.
• Link: https://github.com/ivankovic/omnidiff

2. syscall.sh: full system call tables for 27 architectures, Linux 3.3 through 7.3, with an API

• What it is: When you're writing assembly, working on eBPF, building seccomp rules for container sandboxes, or doing reverse engineering, that syscall number table is basically a daily Google search. The problem is that most tables online are either x86-only or three years stale. syscall.sh takes the job seriously: 27 architectures, Linux 3.3 through 7.3, with a JSON API attached.
• Recent buzz: 208 points and 50 comments on Hacker News.
• Standout features: First, each architecture page lists every syscall's number, arguments, registers, and the instruction to enter the kernel: syscall for x64, svc #0 for arm64. The arm64 page spells out that the number goes in x8, arguments go in x0 through x5, and then svc #0. Second, the data is generated directly from kernel source (including SYSCALL_DEFINE macros), every table is downloadable as JSON, and it marks which version a given syscall was added or removed in. Third, the JSON API covers 27 architectures and ABIs plus every release since 3.3, including calling conventions, Kconfig gating, and diffs between versions. The v2 error format uses RFC 9457 problem details, which script writers will appreciate.
• Getting started: Just open the site, no installation at all. To use it in a script, hit curl https://api.syscall.sh/v2/syscalls/x64/read, or just grab the full-table JSON from something like /x64/syscalls.json and process it yourself.
• How it compares: Static lookup tables like filippo.io's only cover x86 / x86_64. This one is 27 architectures multiplied by the full version history from 3.3 to 7.3, with data auto-generated from kernel source. Back in the 2023 HN thread people were already saying it was more up to date than comparable tables and covered x86, arm, and aarch64.
• Who it's for: Anyone doing systems programming, eBPF, or sandbox escape research, or DevOps folks who just want a bookmark that won't go stale.
• Link: https://syscall.sh/

3. unslop: a cure for interfaces that scream "an AI made this"

• What it is: Frontends vibecoded with an AI assistant have all the functionality, but the screen always looks identical: purple gradients, glow effects, gradient text, and a "New ✨" tucked in the corner. unslop is a Claude Code / Codex skill built to turn that kind of interface into a design with its own personality. It doesn't hand you new components; it runs a staged design audit and rework pass over your existing screens.
• Recent buzz: A project less than 30 days old, already at 6,324 stars on GitHub.
• Standout features: First, the workflow starts by deriving a design direction from the product itself, then works through spacing, color and icons, copy, typography, layout, details, and finally visuals and motion. Second, it carries a very concrete list of AI tells to hunt: purple gradients, glow effects, gradient text, emoji labels, "New ✨" badges, glossy color blocks, all-caps wide-tracked labels, breathing/pulsing animations, and inconsistent spacing. It supports React, Tailwind, HTML, and CSS, across dashboards, apps, and landing pages. Third, it produces unslop-story/story.html, packaging the original screen plus its styles into a single standalone file, with meta tags in the head recording which passes were applied so you can trace back later. Hero image generation is optional and requires hooking up a service like fal, Replicate, or OpenAI images. If nothing is connected, it offers to add an MCP server first, and it asks before running any paid generation.
• Getting started: git clone then mkdir -p /.claude/skills && cp -r unslop/skills/unslop /.claude/skills/ and you're installed. For a single project only, copy it into that project's .claude/skills/. On the Codex side, use $skill-installer 直接從 repo 安裝。裝完在 Claude Code 打 /unslop、在 Codex 打 $unslop.
• How it compares: It runs in the opposite direction from component libraries like shadcn/ui or Tailwind UI. It doesn't add components, it audits what's already on screen. The caveat, stated plainly: it only runs inside Claude Code or Codex. It's not a standalone CLI or a web tool, so if you don't use either of those, set expectations accordingly. The license is CC-BY-4.0, so remember to attribute when you adopt it.
• Who it's for: Engineers shipping AI-generated frontends daily with no designer to call for help.
• Link: https://github.com/heydamir/unslop

Closing

All three of today's picks share something: they save you the time you'd otherwise spend eyeballing a screen for differences. OmniDiff compares code and files, syscall.sh compares versions and architectures, and unslop compares your interface against what a non-AI-looking interface would be. If you only install one today, I'd pick OmniDiff. One brew command changes how every future code review feels. Same time tomorrow, we'll dig up some new ones. I'm Muyan, this has been the Open Source Daily, see you next time.