Skip to Content

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

Tares runs a crew of Claude Code sessions that turns a test coverage project into tickets, each ticket becoming one pull request. The reviewer holds every pull request to a fixed bar, and nothing merges until the reviewer passes it and CI is green. You describe the coverage work once with tares factory spec, and the crew builds it while you answer only the questions that are really yours.

How it works

The software factory for Claude Code is a crew that runs in the background on your machine. For test coverage, the work flows like this:

  • Spec. You describe the coverage you want. Claude Code interviews you one question at a time, a second model challenges the plan, and the result lands in Tares as a spec, milestones with acceptance checks, tickets with a working doc each, and an AGENTS.md.
  • One ticket, one pull request. A builder takes a ticket, works on its own branch and opens a pull request. Builders are started per milestone and repo, so a coverage project can be split by milestone.
  • Review to a fixed bar. The reviewer reviews every pull request and posts its verdict on it. If it asks for changes, the builder makes them and a new review round runs.
  • Merge. Once the reviewer passes and CI is green, the builder merges. You can instead choose to approve every merge yourself.

The project page shows each ticket with its builder, pull request and review rounds. The end-to-end walkthrough follows a real project whose first milestone was tests and CI: Vitest, unit tests for the existing logic, and a CI check on every pull request. It ran as eight merged pull requests. Most passed review on the first round, and two needed a second.

The reviewer can also find smaller issues outside the ticket it is reviewing. In that project the orchestrator turned them into a new ticket and placed it before the integration tests, so the plan grew by one ticket on its own.

Set it up

Follow these steps in this order. Steps 3 and 4 are for a local Tares. On Tares Cloud, use tares login instead.

  1. Check that Claude Code is signed in on a plan that allows background sessions, that git, jq and curl are installed, and that gh is signed in with write access to the repos the crew works in.

    gh auth login
  2. Install the CLI.

    uv tool install tares # or: brew install glassflow/tap/tares
  3. Local only: start Tares. The console opens at http://127.0.0.1:8787.

    tares up
  4. Local only: in a second terminal, start the MCP endpoint every crew session shares. The crew reaches a local Tares only through it.

    tares mcp --transport streamable-http

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

  5. 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 and pick the repos.

  6. Bring up the crew. The first run asks how far it may go: merge on its own after review and green CI, or wait for your yes, whether a second model checks every commit, and how many builders run at once.

    tares factory crew up
  7. Only now plan the project. Run it in the repo you want covered, and put the kind of work in your idea.

    tares factory spec "what you want to build"

    Replace the text with your coverage goal, for example the area to test and that CI must run the tests on every pull request. When the interview ends, say yes to hand the project to the crew.

  8. Answer questions in the orchestrator’s session, and watch the Crew page.

    tares factory crew attach orchestrator

The Get started page has the full quickstart, and tares factory doctor checks everything the crew needs.

What you get

  • Coverage in reviewable pieces. Each ticket is one branch and one pull request, so you can read every change the crew makes on its own.
  • Nothing merges unreviewed. The reviewer posts a verdict on every pull request, and a merge needs a pass plus green CI.
  • Acceptance checks per milestone. The spec sets what done means for each milestone, such as a CI check running on every pull request.
  • A written record. The project page keeps the docs, tickets, review rounds, your answers and every choice the crew made on its own. You check those assumptions at the end of each milestone instead of during every step.
  • Control over merging. Let the crew merge after review, or require your yes before every merge on a project.

When something else fits

  • For a small amount of coverage, work in your own Claude Code session with tares factory session. It plans a small project and builds it there, still on Tares.
  • If your tickets already live in Linear or GitHub Issues, link them to the project. Tares reads them and does not write to them.
  • The crew is built for solo developers and very small teams who already use Claude Code, running on one machine against your own GitHub repos.

Still stuck? Get help

Last updated on