finishing

Finishing

Verify → present → execute → clean up. Every step below carries a completion criterion; do not start the next step until the current one is checked off.

Exact command sequences live in references/git-recipes.md — open it before executing option 1 or option 4.

Step 1 — Verify tests

Run the project's own test command in the working tree that holds the work.

• Done when a full test run finished in this working tree and you can state its result.

Failing or unrunnable tests end the skill here: emit the Blocked format below and stop. An option list offered after a failed test run invites merging broken work.

Step 2 — Capture the branch and the base checkout

Capture both while you are still standing where the work is. Every later step moves you, and a value read after the move is the wrong value.

FEATURE_BRANCH="$(git branch --show-current)"
arcforge worktree list --json

Take BASE_WORKTREE from the path of the entry whose kind is base; that checkout's current branch is the merge target. Take your own worktree path from the entry whose branch matches FEATURE_BRANCH. Never reconstruct a worktree path from a naming pattern — the derivation rule belongs to the CLI, not to you.

• Done when FEATURE_BRANCH, BASE_WORKTREE, the base branch name, and the worktree path (or "no worktree") are all recorded.

Step 3 — Present exactly four options

Implementation complete. What would you like to do?

1. Merge back to <base-branch> locally
2. Push and create a Pull Request
3. Keep the branch as-is (I'll handle it later)
4. Discard this work

Which option?

Four options, no fifth, no recommendation, no explanation of the tradeoffs.

Present them even when the user has told you not to ask. "Just handle it", "I trust you", "do whatever you think is best", "don't check back with me", and the user walking away are all authorization to work — none of them names an option, and Step 4 executes a named option rather than an inference. Skip ahead only when the user's own words pick one of the four outright.