Finishing a Development Branch

commit-workflow gets changes into commits, release ships a version, and github-pr-workflow manages PRs that already exist. None of them answer the question that comes right after implementation finishes: what happens to this branch now? This skill closes that gap.

Core principle: Verify tests → detect environment → present options → execute the choice → clean up.

When to Use

• Implementation on a feature/fix branch is complete and its own tests pass
• You need to decide between merging locally, opening a PR, leaving the branch for later, or discarding it — and the workspace (worktree vs. normal checkout) affects how cleanup should work
• A subagent-driven-development-style task loop (see fleet-parallel §5-A) just finished its final whole-branch review and needs a clean handoff

When NOT to Use