Overview · Use · Publish · Bot format · Safety

GitBot Library

Ready-made bots for GitBot. Read one, install it, and put it to work in your own folders.

GitBot turns Claude Code, Codex, or OpenCode into reusable bots that run on your machine. This repository is the public catalog behind GitBot's Marketplace. Every listing includes the bot's instructions, settings, and optional setup steps in plain files you can inspect before installing it.

Use the Library

First, install and start GitBot:

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

Then:

1. Open GitBot and go to Marketplace.
2. Choose a bot and review what it does, its instructions, setup steps, agent, and permissions.
3. Select Install to add it to your machine.
4. Start a thread in the folder where you want it to work.

GitBot needs Node.js 18 or newer and at least one supported coding agent installed and signed in. See the GitBot README for the full requirements.

Before you install

[!WARNING]
A bot is a set of instructions for an AI coding agent running with your file and shell access. Read its files and permission mode before installing it, just as you would inspect a script from the internet.

A bot may include one-time setup instructions that run after installation. Prefer bots whose behavior you understand, keep approvals enabled when trying one for the first time, and use GitBot only on a trusted network. Read the GitBot README before giving a bot broader permissions.

Publish a bot

You can publish with an agent or prepare the files yourself.

Ask an agent to prepare it

Give Claude Code, Codex, or OpenCode the publish-prompt.md instructions. The agent can find an existing local bot or help shape a new one, validate the listing, show you the final diff, and wait for your approval before opening a pull request.

Create it manually

Read the contributing guide and bot schema, then open a pull request containing one new folder under bots/.

bots/<slug>/
  bot.json           listing, mascot, agent, and permissions
  instructions.md    the bot's standing job
  setup.md           optional one-time setup requirements

Keep submissions portable: no local paths, private repository names, credentials, personal machine details, images, or binaries.

What a published bot contains

• A clear listing with its name, description, category, features, example prompt, and author.
• Readable instructions that define the job the agent performs in every thread.
• Runtime settings for its agent, permission mode, optional model, and tool limits.
• A GitBot mascot selected by body, color, and activity tokens.
• Optional setup instructions only when the job genuinely needs machine preparation.

The repository's generated index is maintained separately. Contributors add a bot folder and never edit index.json or verified.json directly.

Review and contribution

Each pull request should publish one bot. Review checks the schema, file layout, field limits, author, and common privacy mistakes. Maintainers also check whether the instructions deliver what the listing promises and whether the requested permission mode fits the job.

Have an idea without a finished bot? Open an issue and describe the job it should perform.

Links

• GitBot source and documentation
• GitBot on npm
• Contributing guide
• Bot folder specification
• Agent publishing prompt