Automate post-merge git cleanup with remote merge verification and safe branch deletion.
npx skills add https://github.com/wilsonfaustino/ai-tools --skill post-merged
Please help me install this Agent Skill. Skill: post-merged Source: https://github.com/wilsonfaustino/ai-tools/tree/main/skills/post-merged Command: npx skills add https://github.com/wilsonfaustino/ai-tools --skill post-merged
After merging a pull request, developers often leave behind messy local git state: unswitched branches, unpruned local feature branches, and unverified merge status, which can lead to accidental data loss or confusion in future work.
Use the post-merged skill right after you finish shipping a PR to handle all post-merge cleanup steps safely.
High-intent search queries and answers about installing and using this skill.
To clean up local git branches after a pull request merge, you need a workflow that verifies remote merge status, switches to the default branch, and safely deletes the feature branch. This prevents messy local git state and accidental data loss.
Git branch deletion fails after a squash merge because squash merges break local ancestry checks, making Git think the branch is unmerged. Verifying the remote pull request merge status via GitHub CLI bypasses this local ancestry limitation.
You can automatically switch to the default branch and pull latest changes by detecting the repository's default branch dynamically without hardcoding main or master. Pulling with fast-forward only ensures a clean update to your local default branch.
The safest way to delete local feature branches uses safe delete flags that refuse to remove branches with unmerged work. Prompting for explicit user consent before deletion and checking for a dirty working tree prevents accidental data loss.
Yes, post-merge cleanup works with repositories using non-standard default branch names by automatically detecting the repository's configured default branch. It avoids hardcoded main or master assumptions during default branch switching and deletion workflows.
A limitation of using GitHub CLI for post-merge git hygiene is that it cannot automatically force-delete branches with unmerged work, requiring manual intervention. It also only surfaces orphaned gone branches for manual cleanup rather than removing them automatically.
CareCard-caMerge GitHub pull requests and clean up branches after validation.
d3mingDelete local Git branches with removed remote tracking branches and their worktrees.
julianobarbosaAutomate Git commit, branch, merge, and PR workflows with GitHub CLI and security checks.
vobbilisEnforce pre-merge verification and clean merge strategies for Git workflows.
