Finishing a Development Branch
Overview
Guide completion of development work by presenting clear options and handling chosen workflow.
Core principle: Verify tests → Present options → Execute choice → Clean up.
The Process
Step 1: Verify Tests
Before presenting options, verify tests pass:
npm test / cargo test / pytest / go test ./...
If tests fail:
Tests failing (<N> failures). Must fix before completing: [Show failures] Cannot proceed with merge/PR until tests pass.
Stop. Don't proceed to Step 2.
If tests pass: Continue to Step 2.
Step 2: Determine Base Branch
git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null
Or ask: "This branch split from main - is that correct?"
Step 3: Present Options
Present exactly these 4 options:
Implementation complete. What would you like to do?
- Merge back to <base-branch> locally
- Push and create a Pull Request
- Keep the branch as-is (I'll handle it later)
- Discard this work
Which option?
Don't add explanation - keep options concise.
Step 4: Execute Choice
Option 1: Merge Locally
git checkout <base-branch> git pull git merge <feature-branch> <test command> # Verify tests on merged result git branch -d <feature-branch> # If tests pass
Then: Cleanup worktree (Step 5)
Option 2: Push and Create PR
git push -u origin <feature-branch>
gh pr create --title "<title>" --body "$(cat <<'EOF'
Summary
<2-3 bullets of what changed>
Test Plan
- <verification steps> EOF )"
Then: Cleanup worktree (Step 5)
Option 3: Keep As-Is
Report: "Keeping branch . Worktree preserved at ."
Don't cleanup worktree.
Option 4: Discard
Confirm first:
This will permanently delete:
- Branch <name>
- All commits: <commit-list>
- Worktree at <path>
Type 'discard' to confirm.
Wait for exact confirmation.
If confirmed:
git checkout <base-branch> git branch -D <feature-branch>
Then: Cleanup worktree (Step 5)
Step 5: Cleanup Worktree
For Options 1, 2, 4:
git worktree remove <worktree-path>
For Option 3: Keep worktree.
Quick Reference
Option Merge Push Keep Worktree Cleanup Branch
- Merge locally ✓
✓
- Create PR
✓ ✓
- Keep as-is
✓
- Discard
✓ (force)
Red Flags
Never:
-
Proceed with failing tests
-
Merge without verifying tests on result
-
Delete work without confirmation
-
Force-push without explicit request
Always:
-
Verify tests before offering options
-
Present exactly 4 options
-
Get typed confirmation for Option 4
-
Clean up worktree for Options 1 & 4 only
Attribution
Based on obra/superpowers finishing-a-development-branch skill - 152+ installs.