wrap-up

/wrap-up

Run this once a task's PR has merged. It tears down the per-task workspace and returns you to a clean main. It is the inverse of /pickup-task.

Skill ↔ verb contract: this skill owns the UX (scope detection, the merged gate, previews, confirmations, branch deletion, the main fast-forward). The worktree removal itself goes through the verb — forge orchestrate gc --remove-worktrees — which owns the eligibility + lease state machine. The skill NEVER removes a worktree directory by hand and NEVER mutates orchestrator state directly.

Modes:

• default — wrap up a single task (the one whose worktree you are in, or one you pick from the candidate list).
• --all — batch: wrap up every terminal-state task with a merged PR, behind a single confirmation.

---

Safety contract (do not drop these clauses)

These four gates are non-negotiable. A future edit must keep every one.

Unmerged-abort gate

The PR-merged check runs BEFORE anything is deleted. If gh pr view reports the branch's PR is not MERGED, abort immediately — NOTHING is deleted (no worktree removal, no branch deletion, no main switch). An open or closed- unmerged PR means the work is not done; wrapping up would orphan it.

Confirmation-before-destruction gate

Worktree removal and branch deletion only run after an explicit user confirmation. Preview the full plan first (worktree path, branch, main delta). Suggest-don't-force: never delete on the same turn you discovered the candidate. In --all mode a SINGLE batched confirmation covers the whole list, shown in full before the prompt.

ff-only refusal on dirty main

Before git switch main && git pull --ff-only, run git status --porcelain in the main checkout. If it is non-empty, refuse the pull and show the porcelain output verbatim so the user can see exactly what is dirty. Never stash, reset, or force. --ff-only itself refuses any non-fast-forward; do not override it.

-D second-confirm

git branch -d <branch> (safe delete) is the default. It fails if the branch is not fully merged into its upstream. Only escalate to git branch -D (force) after a SECOND explicit confirmation — and only after the PR-merged gate has already passed. A -d failure after a merged PR usually means the merge was a squash or rebase; surface that, then offer the -D path.