Bots that catch a link that no longer says what you cited it for #86

A link in your docs goes through a redirect to where the content actually lives now. The checker is happy as long as the redirect resolves, but the page on the other end can get rewritten, merged into a different doc, or replaced with something that no longer says what you cited it for, and nothing fails to tell you.

The part a bot can get definitively right is the diff: fetch what the redirect currently resolves to, compare it against what was there when the link was last verified, and flag when they've drifted apart. The part it has to bring to a person is judgment: a reworded paragraph that says the same thing isn't a regression, but a redirect that now lands on a different section, a different version, or a parked domain is.

We'd take one per content type: docs pages, package registries, and API references all redirect, and what counts as "still the same" differs across them.

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.