Worktree Remove

3. Check Merge Status

• Check if the feature branch has been merged into the base branch:
  • git branch --merged <base-branch> from the main worktree
  • Or check if a PR was merged via gh pr list --head <branch> --state merged if gh is available
• If the branch has NOT been merged, warn the user clearly. Do not delete the branch unless they explicitly confirm.

4. Remove the Worktree

git worktree remove <worktree-path>

• If removal fails due to unclean state and the user has confirmed they want to discard, use git worktree remove --force <worktree-path>
• Run git worktree prune to clean up stale worktree references

5. Optionally Delete the Branch

• If the branch was merged, offer to delete it:
  • Local: git branch -d <branch-name>
  • Remote: git push origin --delete <branch-name>
• If the branch was NOT merged, only delete with git branch -D if the user explicitly requests it

6. Verify Cleanup

• Run git worktree list to confirm the worktree is gone
• Run git branch to confirm branch state
• Report what was removed

Notes

• Safety is the priority: never silently discard uncommitted work
• Always show the user what will be lost before any destructive action
• If the worktree directory was already manually deleted, git worktree prune handles the cleanup