finishing-a-development-branch

To finalize a Git branch after tests pass, this workflow presents four deterministic options: merge via pull request, create a PR for later review, keep the branch for ongoing work, or discard the work entirely.

The best way to clean up a Git worktree after merging is to use a branch finalization workflow that coordinates optional worktree cleanup alongside base-branch detection and integration, ensuring no orphaned worktrees remain after the merge.

Yes, you can create a pull request without merging right away by selecting the explicit option to generate a PR for later review, leaving the current branch intact for ongoing development while awaiting approval.

Yes, this Git branch cleanup workflow integrates directly with the merging-to-main skill, enabling automated PR creation and execution handoff when you select the option to merge your completed feature branch via pull request.

Base-branch detection works by automatically verifying the parent branch before integration, ensuring the completed feature branch merges into the correct target rather than an incorrect or outdated mainline branch.