finishing-a-development-branchlisted

# finishing-a-development-branch The work is committed and green. Now decide where it goes. Routed to by `/feature` and `/sprint` after `commit-gate` clears — never before. ## Pre-flight Read these, or STOP and surface the gap — never guess the branch name or the default branch: - `<project-root>/.codearbiter/CONTEXT.md` — the default-branch name and project context. - `<project-root>/.codearbiter/plans/<slug>.md` — the plan this branch executed, when `/feature` or `/sprint` produced one. The yardstick for "is the work complete." - `<project-root>/.codearbiter/last-checkpoint` — the most recent gate results; confirms `commit-gate` cleared on this branch. `commit-gate` MUST have cleared on the current HEAD. If it has not, this skill does not run — return to it. ## Phase 1 — State assembly · gate: BLOCK Assemble the facts the decision needs. Nothing is presented until all are in hand: - **Branch** — the current branch name and its base. Confirm it is NOT the default branch; if HEAD is the default branch, STOP — there is nothing to finish and merge-to-default is forbidden. - **Diff summary** — files changed, insertions/deletions, and the commit list since the base. Read it, do not paraphrase from memory. - **Gate results** — `commit-gate` outcome and the `last-checkpoint` record. Surface any open `[NEEDS-TRIAGE]` markers left in the diff as out-of-scope findings. - **Plan delta** — when a plan exists, state which plan items the branch satisfied and which remain open. Ope