Walkthrough

Ship It: Branches, PRs, and the Human Merge

Agents branch, commit, push, and open the PR. The merge stays human.

Antigravity agents use the same terminal you do: they can branch, commit, push, and open a PR with the gh CLI. Draw the line at merge — that stays human. An agent's own walkthrough is evidence, not independent review; the merge click is where independent review happens.

Steps · 0 / 3 done

Set the ground rules once
Put the git contract where every agent will load it — your workspace rules / knowledge. Allowed: branch, commit, push, open PRs. Never: merge, force-push, commit directly to main.
```
# Git rules for agents
- Work on a branch named feat/<task-slug> or fix/<task-slug>.
- Conventional commit messages; one logical change per commit.
- Open PRs with `gh pr create`; body = walkthrough summary + evidence links.
- NEVER merge, never force-push, never commit to main directly.
```
VerifyA fresh agent, asked to ship a change, branches and opens a PR without being reminded — and stops there.
Let the agent open the PR
The PR body should be the walkthrough in miniature: what changed, why, and the evidence.
```
Open a PR for this task: branch feat/health-endpoint, conventional commit, PR body from your walkthrough — include the test output and the response screenshot.
```
VerifyThe PR exists with an evidence-rich body. Reviewers see proof, not prose.
Keep the merge human
Review the walkthrough, then the diff, then merge it yourself. If you catch yourself rubber-stamping, tighten — read the diff first for a week.
```
gh pr view --web
```
VerifyEvery merged agent PR has a human approval on it. No exceptions, including 'trivial' ones.

Check your understanding

Q1. Why does the merge stay human even when the agent's evidence looks complete?

· Tick off the 3 step(s) above.

· Score 100% on the quiz.

Ship It: Branches, PRs, and the Human Merge

Set the ground rules once

Let the agent open the PR

Keep the merge human