Skip to Content

How can I get Claude Code to take on docs updates on its own, with every change reviewed before it merges?

Tares runs a crew of Claude Code sessions that turns a plan for your docs updates into tickets, one pull request each, and its reviewer reviews every pull request before it merges. You describe the docs work once with tares factory spec, and builders take the tickets one at a time. Nothing merges until the reviewer passes it and CI is green, and you can also require your own yes before every merge.

How it works

The software factory for Claude Code is a crew: an orchestrator, a reviewer and builders. You talk only to the orchestrator.

  • The plan sets the ticket list. In the spec interview you say what the docs updates are. Claude Code asks one question at a time, a second model challenges the plan, and the result lands in a Tares project as a spec, milestones with acceptance checks, tickets with a working doc each, and an AGENTS.md.
  • One ticket is one unit of work on one branch. A builder takes a ticket, works on its own branch and opens a pull request. Builders work through their tickets one at a time, and the working doc travels with the ticket.
  • The reviewer holds every pull request to a fixed bar. It posts its verdict on the pull request. If it asks for changes, the builder makes them and a new review round starts.
  • Merging follows the verdict. The builder merges once the reviewer passes the pull request and CI is green. At crew up you choose whether the crew merges on its own after review and green CI, or waits for your yes. A single project can also wait for your yes before every merge while the rest of the crew merges on its own.
  • The ticket list can grow. When the reviewer finds smaller issues outside the ticket it is reviewing, the orchestrator turns them into a new ticket and places it in the plan.

The plan, tickets, reviews and your answers are kept on Tares, so a crew that restarts carries on where it stopped. A project, end to end shows this on a real project.

Set it up

You need Claude Code signed in on a plan that allows background sessions, gh signed in with write access to the repo that holds your docs, and git, jq and curl.

  1. Sign in to GitHub with gh, then install the CLI.

    gh auth login uv tool install tares # or: brew install glassflow/tap/tares
  2. For a local Tares, start it, then start the MCP endpoint every crew session shares in a second terminal. Stations reach Tares only through this endpoint.

    tares up # console on http://127.0.0.1:8787 tares mcp --transport streamable-http # http://127.0.0.1:8788/mcp

    On Tares Cloud, run tares login instead and pick your workspace in the browser. There is no MCP endpoint to start.

  3. Give Tares access to GitHub, so it can read the pull request, CI and merge state of every ticket. On a local Tares, add a token or App under Settings > GitHub. On Tares Cloud, choose Connect GitHub. The Get started page has both paths.

  4. Bring up the crew. The first run asks how far the crew may go. For a review-before-merge setup, either keep merging on its own after review and green CI, or choose to wait for your yes.

    tares factory crew up
  5. In the docs repo, plan the work. Name the docs updates you want, and shape the ticket list while Claude Code interviews you.

    tares factory spec "what you want to build"
  6. When it asks whether to hand the project to the crew, say yes. Then open the orchestrator to answer its questions.

    tares factory crew attach orchestrator

Run tares factory doctor at any point to check everything the crew needs.

What you get

  • Every pull request reviewed. The reviewer reviews each one to a fixed bar and posts its verdict, and the builder does not merge before it passes with CI green.
  • A record of each ticket. The Tickets fold on the project page shows each ticket with the builder that held it, its pull request and its review rounds.
  • Your choice of merge control. Let the crew merge after review and green CI, or have it wait for your yes. Your answers are recorded in your own words under Decisions.
  • Choices written down. When the plan does not cover something, the crew picks an answer and records it as an assumption. The orchestrator brings the assumptions to you at the end of each milestone, so you check them once instead of at every step.
  • Follow-up tickets. Smaller issues the reviewer finds become new tickets in the same project.
  • Progress at a glance. The Crew page shows the question waiting for you, each station, each open project with its builders, and the pull requests waiting for review.

When something else fits

  • For a small change, tares factory session works a project in your own Claude Code session, still on Tares, without bringing up the crew.
  • If your tickets already live in Linear or GitHub Issues, the project can keep them there. Tares reads them and never writes to them.

Still stuck? Get help

Last updated on