Skip to main content
When a run completes successfully, UseZombie opens a pull request on the connected GitHub repository. Here is what that PR looks like and how it is constructed.

Branch naming

Every run gets a dedicated branch:
zombie/<run_id_short>/<spec_slug>
For example:
zombie/01JQ7K/add-healthz-endpoint
The branch is created from the base branch HEAD at the time the run starts. The exact base commit SHA is recorded on the run row for traceability.

Isolated worktree

Each run executes in an isolated git worktree checked out from the base branch HEAD. This means:
  • Runs cannot interfere with each other, even when running in parallel.
  • The worktree is cleaned up automatically after the run completes.
  • No leftover branches or temporary files persist on the worker.

PR body

The PR body contains an agent-generated plain-English explanation of what changed and why. This is not a diff summary — the agent writes a narrative description of the implementation decisions it made, based on the spec it was given. Example:
## What this PR does

Adds a `GET /healthz` endpoint that returns the server status and package
version. The version is read from `package.json` at startup and cached.

A unit test covers the happy path — verifying the 200 status code and
JSON body shape.

Scorecard comment

A separate PR comment is posted with the run’s scorecard:
FieldValue
Score87 (Gold)
Completion100
Error rate85
Latency72
Resource efficiency50
Wall time3m 12s
Token consumption14,200
The comment also includes a gate results table:
GateResultLoops
lintPASS1
testPASS2
buildPASS1

Human review required

In v1, all PRs require human review. There is no auto-merge. You review the PR like any other — approve, request changes, or close it.
Coming soon: the PR description will include a quality badge showing the agent’s tier and score, for example “This PR was produced by a Gold-tier agent (87/100).”
Score-gated auto-merge is planned for v2. When enabled, runs that exceed a configurable score threshold will be merged automatically.