| name | worktree-merge |
| description | Merge the current forge worktree back to the default branch through the 4-gate verification chain (tests, lint, adversarial review, summary) and a locked rebase. Use when finishing a worktree session or asked to merge work back. |
Follow the worktree merge workflow in .opencode/rules/worktree-workflow.md (steps 3–8). Do not skip any gate unless the user explicitly says "skip gate X".
Run all four gates in order. Any failure stops the merge and leaves the worktree intact for inspection — never delete a worktree on a failed merge.
-
Sanity check — confirm CWD is inside a worktree (git rev-parse --git-common-dir differs from .git). If not, refuse and tell the user to /worktree first.
-
Gate 1 — Tests. Detect changed modules from git diff --name-only origin/master... and run the project's targeted test command:
echo "FORGE: Gate 1 test command not configured — run /forge-init before merging" >&2
exit 1
For long runs, launch the build in the background (Bash run_in_background, or ./cmd > log 2>&1 &) and poll the log.
-
Gate 2 — Lint / type checks. Run the project's lint / type checks per [[commit-workflow]] Step 2.
-
Gate 3 — Adversarial review. Spawn review-final subagent on git diff origin/master...HEAD. Block on BLOCK verdict. Quote any concerns back to the user.
-
Gate 4 — Summary & proceed. Under the DVRR operating model (.opencode/rules/operating-model.md), gates 1–3 are the authority — they replace human pre-approval. Show:
git diff --stat origin/master...HEAD- List of changed files
- Gate 1/2/3 results in one line each
Then proceed automatically to the locked rebase. Do NOT wait for approval. Fail-closed: if any of gates 1–3 did not return a clean PASS, stop and leave the worktree intact. A user can interject at any time to halt.
-
Locked rebase (linear history — never a merge commit). The lock lives in the shared git common dir (inside a worktree .git is a pointer file, not a directory): LOCK_FILE="$(git rev-parse --path-format=absolute --git-common-dir)/agent-rebase.lock". Check command -v flock first — flock is absent on stock macOS; if missing, use the mkdir-based mutex documented in the rule (same common-dir location) — never skip the lock. Time the wait to acquire flock --timeout 300 "${LOCK_FILE}" (e.g. capture an epoch before and after the flock), then inside the lock:
git fetch origin master --quiet
git rebase origin/master
git push origin HEAD:master
Always rebase, never merge — master is kept a strictly linear history with no merge commits. Do NOT git merge the worktree branch into master, do NOT use git pull without --rebase, and when several worktrees are ready, rebase them one at a time under the lock (never via an intermediate "integration branch"). See .opencode/rules/worktree-workflow.md → Linear History — No Merge Commits.
Serialisation telemetry (§18.7 / [[decision-log]]). If the lock wait was non-trivial, record serialisation.merge_lock_s (seconds waited on flock) into this unit's .tmp/decisions/<id>.md telemetry block. If the rebase hit conflicts, also record serialisation.contention_s (seconds spent resolving them).
-
Re-verify the integrated result (spec §8.4). If the rebase in step 6 pulled in other units' commits (i.e. origin/master advanced since the worktree branched), re-run the Gate 1 test command against the integrated tip before cleanup — passing in isolation does not prove the merged result passes. If the rebase was a clean fast-forward with no new upstream commits, this is a no-op.
-
Cleanup. On successful push only:
cd "$(git rev-parse --show-toplevel)/.."
git worktree remove "${WORKTREE_DIR}" --force
git branch -D "${BRANCH}"
rm -f .tmp/active-worktree
-
Report. Summarise to the user: gate results, commit hash on master, worktree cleaned up.
If the user provided additional instructions (e.g. "skip user approval", "skip tests because we already ran them"): $ARGUMENTS — only honour explicit skip flags, never silently drop a gate.
