Who it is forA bot author who wants to contribute a working bot to the Git Bot Library for others to use.
The problemWriting a clear public listing and a correct pull request for a bot takes careful review.
The outcomeA reviewed draft listing and a pull request prepared only after you approve the listing and final diff.
What you need first
- Node.js 18 or newer
- At least one installed, signed-in coding agent: Claude Code, Codex, or OpenCode
- A local folder that holds the repos you want the bot to work in
Steps
- Open the bot in the Bots panel and select Publish to Marketplace.
- Copy the prompt and paste it into a conversation with the bot.
- Review the draft listing the bot shows you.
- Review the final diff before approving, since the bot waits for your approval.
- Check the Git Bot Library publishing guide if you prefer to submit a listing yourself.
Prompt for your agent
Using the gitbot-hq/GitBot package, open <bot name> and run Publish to Marketplace in its conversation. Expected output: a draft listing and a final diff shown to the user before any pull request is prepared. Verify that copying the prompt alone published nothing and that the bot waited for approval.
Caveat. Copying the prompt does not publish anything, and Marketplace bots are reviewed through pull requests in the Library repository.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page