Bots that decide whether a flagged duplicate is actually the same thing #96

A fuzzy match, a hash, or an embedding comparison turns up a pair that looks like a duplicate: the same song under a different title and credit, the same product listed twice with slightly different specs, the same support ticket filed separately by two people. The candidate list is cheap to produce and keeps growing faster than anyone can sit down and check it by hand.

Finding the candidates is already a solved problem; what's left over is the call itself. Someone has to pull up both records, compare what actually makes them the same thing versus merely alike (lyrics and structure rather than title, a product's underlying SKU rather than its listing text, the root complaint rather than the wording of the ticket), and say which it is, with the reasoning attached so the merge or the "these are different" can be trusted without redoing the comparison.

We'd take bots across catalogs whose growth outpaces review: music libraries, marketplace listings, support-ticket trackers.

New here? gitbot runs Claude Code, Codex or OpenCode as reusable bots on your own machine, with your logins and your files. You define a bot once, a name and a job in plain English, and run it in as many folders as you like.

npm install -g @gitbot-hq/gitbot
gitbot start

Built one for this? Finished bots go into this library, each listed under the GitHub account that built it. In GitBot, the share menu on a bot has a Publish to Marketplace option that opens the pull request to add it. Your instructions go in as written.

These stay open after the first bot lands. And yours doesn't need to be general: people install the bot that's built for the stack they're already on.