---
name: gitback-get-started
description: |-
  Hand your coding agent this playbook to set up Gitback: install the Gitback
  skills, connect the Gitback MCP server, then fill the Board's FAQ, changelog
  and roadmap from your repo.
title: 'Onboard your agent to Gitback'
url: https://gitback.us/get-started.md
---

# Set up Gitback for your AI coding agent

Use this playbook to prepare the current agent for Gitback, the feedback, roadmap, changelog and FAQ board built from a GitHub repository. Install the skills and the MCP connection once per coding agent, then run the skills inside the repo whose Board the user is setting up.

## How to run

Run sections 1 and 2 once per coding agent. Run section 3 inside the user's repository. In section 1, try the plugin route first and use the standalone skills only if the agent has no plugin support.

Perform actions yourself when terminal or file access is available. Install for the user, not for one project. Pause only for user sign-in, approval, or UI actions you cannot perform. Do not merely return commands for the user to copy. If a step is blocked, record why and continue with the remaining steps.

## 1. Install the Gitback skills

The skills live in https://github.com/Coduo-Studio/gitback-skills. Each one fills part of the Board from the repo and hands the user a pull request to review; nothing lands on the default branch without them. The plugin also connects the Gitback MCP server, so section 2 is only needed when you install the standalone skills.

### Claude Code

```bash
claude plugin marketplace add Coduo-Studio/gitback-skills
claude plugin install gitback@gitback
```

### Codex

```bash
codex plugin marketplace add Coduo-Studio/gitback-skills
codex plugin add gitback@gitback
```

### Cursor, GitHub Copilot and other agents

Use this when the agent has no plugin support. It installs the skills only:

```bash
npx skills add Coduo-Studio/gitback-skills
```

Confirm the `gitback-faq`, `gitback-changelog`, `gitback-roadmap` and `ask-gitback` skills are available to the agent.

## 2. Connect the Gitback MCP server

Skip this for a client where you installed the plugin in section 1.

The server is a remote Streamable HTTP endpoint at `https://gitback.us/api/mcp`. Reads need no sign-in. Tools that write as the user sign in with GitHub over OAuth. Before changing an MCP configuration file, inspect it and merge the `gitback` entry without replacing unrelated settings.

### Claude Code

```bash
claude mcp add --transport http gitback --scope user https://gitback.us/api/mcp
```

### Codex CLI

```bash
codex mcp add gitback --url https://gitback.us/api/mcp
```

If the server asks for sign-in, run `codex mcp login gitback`.

### Cursor

Merge this into `~/.cursor/mcp.json`:

```json
{
  "mcpServers": {
    "gitback": {
      "url": "https://gitback.us/api/mcp"
    }
  }
}
```

### VS Code with GitHub Copilot

Run **MCP: Add Server**, choose **HTTP**, enter `https://gitback.us/api/mcp`, name it `Gitback`, and select **Global**. Then run **MCP: List Servers**, start Gitback, and allow authentication.

## 3. Fill the Board

Run these inside the repository the Board is for. Ask the user which one to start with, or run `ask-gitback` to pick for them.

- `gitback-faq`: drafts FAQ answers from the code, docs, Issues and Discussions into `.gitback/faq/`, opens a pull request, and gives the user a preview link before they merge.
- `gitback-changelog`: sets up GitHub Releases for a repo with no changelog, or one whose changelog lives in `CHANGELOG.md` or a docs site. Forward only: it never backfills old versions.
- `gitback-roadmap`: asks the user a few questions, reads the Issues for evidence, proposes Planned, In progress and Complete, and applies the labels only after the user approves. It prints an undo command.

Each skill ends with a pull request or an approval step for the user. Do not merge on their behalf.

## Next

- Board and pricing: https://gitback.us
- Everything an agent can read about Gitback: https://gitback.us/llms.txt