# AI use cases for Git Bot (gitbot-hq/GitBot)

Repo: [gitbot-hq/GitBot](https://github.com/gitbot-hq/GitBot) | Use cases: 4 | Page: https://dedupedai.com/use-cases/gitbot-hq-gitbot/

GitBot is a local web app that runs Claude Code, Codex, or OpenCode on your machine as reusable bots with persistent threads and permissions you control.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Flag docs that no longer match the code: https://dedupedai.com/use-cases/gitbot-hq-gitbot/flag-stale-docs-in-a-repo/
- Ask Codex about a repo without allowing edits: https://dedupedai.com/use-cases/gitbot-hq-gitbot/read-only-repo-questions-with-codex/
- Share a tested bot with a teammate by code: https://dedupedai.com/use-cases/gitbot-hq-gitbot/share-a-tested-bot-with-a-teammate/
- Publish a bot to Marketplace after review: https://dedupedai.com/use-cases/gitbot-hq-gitbot/publish-a-bot-to-marketplace/

## How to flag docs that no longer match the code with Git Bot

Repo: [gitbot-hq/GitBot](https://github.com/gitbot-hq/GitBot) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Create a reviewer bot that finds one documentation mismatch in a repo and proposes a fix.

**Who it is for:** A maintainer whose README or docs have fallen behind the code and who wants a regular check that asks before any edit.

**The problem:** Documentation drifts after code changes, and finding each mismatch by hand takes time.

**The outcome:** A bot that names one concrete mismatch, explains it, proposes a small fix, and waits for approval before editing files.

### Steps

1. Install Node.js 18 or newer and sign in to the Claude Code CLI.
2. Run `npm install -g @gitbot-hq/gitbot`.
3. Run `cd /path/to/your/projects`, then run `gitbot start`.
4. Open http://localhost:3000, select + in the Bots panel, choose Create manually, and paste the documentation review instructions into Instructions.
5. Keep Permissions on Ask before each tool, open a new thread, choose the repo folder, and send your first message.

### Prompt to paste into your agent

```text
Using the gitbot-hq/GitBot package, install it with npm install -g @gitbot-hq/gitbot, start it from your projects folder, and create a bot whose instructions find one documentation mismatch in <repo folder>. Expected output: one mismatch with an explanation and a proposed small fix, with no file edits until the user approves. Verify that the bot asked before editing any file.
```

### Caveat

Git Bot has no authentication, so keep it on a trusted network and stop it when the review is done.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/gitbot-hq-gitbot/flag-stale-docs-in-a-repo/

## How to ask Codex about a repo without allowing edits with Git Bot

Repo: [gitbot-hq/GitBot](https://github.com/gitbot-hq/GitBot) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Explore an unfamiliar codebase with Codex in Plan only mode, with no file changes.

**Who it is for:** A developer joining a project who wants answers about how it works without risking changes to the files.

**The problem:** Reading an unfamiliar codebase is slow, and an agent with edit access could change files while you are only asking questions.

**The outcome:** Answers about the code from a Codex thread that runs in Plan only mode inside the chosen repo folder.

### Steps

1. Install the `codex` CLI and run `codex login`.
2. Run `npm install -g @gitbot-hq/gitbot`.
3. Run `gitbot start` from the folder that holds your projects, then open http://localhost:3000.
4. Create a bot, choose Codex as the agent, and set Permissions to Plan only.
5. Open a new thread, choose the repo folder, and ask how one feature works.

### Prompt to paste into your agent

```text
Using the gitbot-hq/GitBot package, start it with gitbot start and create a Codex bot with Plan only permissions. Ask it to explain how <feature name> works in <repo folder>. Expected output: a written explanation that names the files it read, with no edits made. Verify that the working files are unchanged after the reply.
```

### Caveat

Codex cannot enforce an Allowed tools list, so Plan only mode is the control to rely on for read-only work.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/gitbot-hq-gitbot/read-only-repo-questions-with-codex/

## How to share a tested bot with a teammate by code with Git Bot

Repo: [gitbot-hq/GitBot](https://github.com/gitbot-hq/GitBot) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Export a bot's settings and instructions so a teammate can import the same bot.

**Who it is for:** A team lead who has tuned a bot on one machine and wants a teammate to use the same setup on theirs.

**The problem:** Rebuilding a working bot's instructions and permissions by hand on another machine is slow and error prone.

**The outcome:** A teammate who imports the bot and gets the same instructions and permissions, without chat history or local files.

### Steps

1. Open the bot you want to share in the Bots panel.
2. Select Share with code and send the code to your teammate.
3. Ask your teammate to select Import bot in Git Bot and paste the code.
4. Have your teammate read the instructions and permissions, and read any setup instructions, before running the bot.
5. Have your teammate confirm the agent in the bot is installed and signed in on their machine.

### Prompt to paste into your agent

```text
Using the gitbot-hq/GitBot package, export <bot name> with Share with code and import it on a second machine with Import bot. Expected output: an imported bot with the same instructions and permissions and no chat history. Verify that the agent named in the bot is installed on the second machine before the first thread runs.
```

### Caveat

Share with code leaves out chat history and local files, but the instructions may still contain private details, so check them before sending.

Risk, remote script: Imported bots may include setup instructions that run when imported, so read them and the permission mode before importing.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/gitbot-hq-gitbot/share-a-tested-bot-with-a-teammate/

## How to publish a bot to Marketplace after review with Git Bot

Repo: [gitbot-hq/GitBot](https://github.com/gitbot-hq/GitBot) | Difficulty: Advanced | Time: 60 minutes | Basis: From the README

Draft a public Marketplace listing with your bot and approve it before any pull request.

**Who it is for:** A bot author who wants to contribute a working bot to the Git Bot Library for others to use.

**The problem:** Writing a clear public listing and a correct pull request for a bot takes careful review.

**The outcome:** A reviewed draft listing and a pull request prepared only after you approve the listing and final diff.

### Steps

1. Open the bot in the Bots panel and select Publish to Marketplace.
2. Copy the prompt and paste it into a conversation with the bot.
3. Review the draft listing the bot shows you.
4. Review the final diff before approving, since the bot waits for your approval.
5. Check the Git Bot Library publishing guide if you prefer to submit a listing yourself.

### Prompt to paste into your agent

```text
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.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/gitbot-hq-gitbot/publish-a-bot-to-marketplace/