Delete a branch locally — AI Prompts for Git

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

Delete the local branch feature/refactor-login on my machine — ensure I switch to main first if I…

Delete the local branch feature/refactor-login on my machine — ensure I switch to main first if I am on that branch, abort if it has unmerged commits, and give me a summary of what would be deleted before final confirmation.

Improve — make it easier to accept

Before I remove this local branch, make it safe to delete: show whether feature/refactor-login is…

Before I remove this local branch, make it safe to delete: show whether feature/refactor-login is merged into main or any release branch, list unpushed commits, and surface any open pull request that references it so I can avoid deleting something still in review.

Decide — diagnose the stuck moment

I attempted to delete feature/refactor-login locally and the tool warned about unmerged commits. I…

I tried to delete a branch and was warned about unmerged work

I attempted to delete feature/refactor-login locally and the tool warned about unmerged commits. I can't remember whether those commits were intentionally kept or accidentally left behind. I need to know if they exist on any remote or on main so deleting won't lose work. What's the best sequence to verify whether those commits are safe to drop or need to be rescued first?

Become — change the pattern

Developers repeatedly delete local branches then later complain they lost staging work because we…

We keep resurrecting local branches we already removed remotely

Developers repeatedly delete local branches then later complain they lost staging work because we didn't check remotes or open PRs. I want a one-minute routine to teach the team so local deletions don't cause data loss or confusion. What specific checks and a short pre-delete checklist should everyone follow?

Next to this one

Other version control work people do in Git.

Configure user name and email Create a bare repository Create a new branch Create a release or tagger Create and apply a patch Delete a branch remotely Discard changes in a file Drop or clear stashes Identify large files Ignore files or directories

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.

The rest of the map

Same library, five ways in.

Work Atlasthe whole map, interactive Careers1,949 jobs and their real tasks Soft skillsthe human part of the work Activities500 things people do Prompt Librarybrowse every prompt