merged

After merging a PR, switch to main with git checkout main, pull the latest changes, then delete the feature branch with git branch -d and remove the remote copy with git push origin --delete. This skill automates all of these steps in sequence.

Use git branch -d for local deletion, which refuses to delete branches with unmerged changes, preventing accidental work loss. For the remote, run git push origin --delete branch-name, optionally suppressing errors if the remote branch was already removed.

The skill detects when the current branch is main or master and stops immediately without making changes. There is nothing to clean up in that state, so no branches are deleted and no checkout occurs.

git branch -d only deletes branches whose commits are fully merged into the current branch. If it refuses, the branch contains unmerged work; either merge it first or use git branch -D to force deletion at the risk of losing commits.

Yes. The remote deletion command uses error suppression with a fallback message, so if GitHub already deleted the branch during the merge, the skill reports that the remote branch is gone and continues without failing.