Bots that adapt something vendored from upstream before it's kept #84

Vendoring something from an upstream repo, a skill, a template, a chunk of config, rarely means taking it as is. Branding needs stripping, paths need to point at your own tree, and sometimes the right move is folding it into something you already have rather than adding a parallel copy next to it. Each of these calls is small on its own, but skipped often enough that vendored content quietly rots: it stays a stranger's artifact instead of becoming yours.

As a gitbot, the job is making that call explicitly every time something is pulled in: what to strip, what to merge, what to rewire, and what to leave alone, before it's committed.

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.