merged

Switch to main, pull latest, and delete merged feature branches.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/heman1033p-create/heman1033p-create.github.io --skill merged-heman1033p-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: merged
Source: https://github.com/heman1033p-create/heman1033p-create.github.io/tree/main/.gemini/skills/merged
Command: npx skills add https://github.com/heman1033p-create/heman1033p-create.github.io --skill merged-heman1033p-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After a PR is merged, this skill automatically cleans up by switching to the main branch, pulling the latest changes, and deleting the merged feature branch to maintain a tidy repository.

Core Features & Use Cases

  • Switch to main and update with the latest commits to ensure everyone works from an up-to-date baseline.
  • Delete local and, if applicable, remote branches that were merged to prevent drift and clutter.
  • Safe-guards ensure you never delete main and only remove branches that have been fully merged.

Quick Start

Run the /merged command to switch to main, pull latest, and delete the merged feature branch.

Frequently Asked Questions about merged

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Git branch cleanup after a PR merge?

Automate Git branch cleanup by switching to main, pulling latest commits, and deleting the merged feature branch. This ensures your local main branch is up-to-date and removes outdated branches to maintain a tidy repository.

What is the safest way to delete local and remote Git branches after merging?

Safe branch deletion checks for a remote branch before removing it and uses safe-delete logic to avoid losing work. It also enforces safety by preventing the deletion of main, ensuring only fully merged branches are removed.

How do I pull latest changes to main and remove feature branches in one step?

You can pull latest changes to main and remove feature branches by running a single command that switches to main, fetches the latest updates, and safely deletes the merged branch both locally and remotely.

Why does my Git workflow leave clutter after a PR is merged?

Your Git workflow leaves clutter because merged feature branches remain locally and remotely. Automating post-merge cleanup switches to main, pulls updates, and deletes these branches to prevent drift and clutter.

Can I prevent accidental deletion of the main branch during Git workflow automation?

Yes, this branch cleanup automation prevents accidental deletion of the main branch by enforcing safety guards. It only removes feature branches that have been fully merged and checks for remote branches before deleting.

When do I need to automate post-merge branch cleanup in a collaborative Git workflow?

You need post-merge branch cleanup in collaborative Git workflows after PR merges to maintain an up-to-date main baseline and clean branch history, preventing drift and clutter across feature branches.