skills.rest
takemi-ohama
takemi-ohamaCOMMUNITY
Explore all skills by this author →
GitHub

merged

Update the main branch and delete the merged feature branch after a PR merge.

Updated Jan 30, 2026
Search Tags:#automation#git#workflow#cleanup#merge#branch-pruning
One-click install
npx skills add https://github.com/takemi-ohama/ai-plugins --skill merged-takemi-ohama
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merged
Source: https://github.com/takemi-ohama/ai-plugins/tree/main/plugins/ndf/skills/merged
Command: npx skills add https://github.com/takemi-ohama/ai-plugins --skill merged-takemi-ohama

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the cleanup tasks that follow a PR merge, ensuring the main branch is current and the feature branch is removed, reducing manual cleanup time and human error.

Core Features & Use Cases

  • Update main: fetch and merge latest from main to ensure the repository is up-to-date after a PR merge.
  • Cleanup branches: delete the merged feature branch to maintain a clean branch namespace.
  • Safe, idempotent operations: performs checks to avoid deleting unmerged branches or duplicating work, and can be retried safely after failures.
  • Use Case: After merging a PR into main, run this skill to finalize integration by syncing main and removing the feature branch.

Quick Start

Update main to latest and remove 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 merging a pull request?▼

Automating post-merge cleanup involves fetching the latest main branch and deleting the merged feature branch. This skill performs these Git workflow tasks automatically to reduce manual effort and maintain consistent branch hygiene.

What is the safest way to delete a Git feature branch after a merge?▼

The safest way to delete a feature branch after a merge is using idempotent operations with built-in safety checks. This skill verifies the PR is fully merged into main before pruning the branch, preventing accidental deletion of unmerged work.

Can I retry a failed Git branch pruning operation without causing errors?▼

Yes, you can retry a failed branch pruning operation safely if the process is idempotent. This skill handles errors gracefully and applies idempotent operations, allowing you to retry post-merge cleanup without duplicating work or corrupting the repository.

How do I sync my local main branch after a pull request is merged?▼

Syncing your local main branch after a pull request requires fetching and merging the latest remote updates. This skill automates this post-merge synchronization to ensure your main branch is up-to-date before pruning the feature branch.

Does this automated post-merge cleanup work with standard Git workflows?▼

Yes, this automated post-merge cleanup is designed for standard Git workflows where PRs are merged into main. It enforces consistent branch hygiene by syncing the main branch and reporting the final state and PR details.

Related Skills

Explore More Software Engineering Skills→
vietlinhh02vietlinhh02

Finishing Development Branch

Automate Git development branch completion with test verification and merge options.

Community
Advanced
chrishuffman5chrishuffman5

upload-skill

Automate publishing skill folders to the main branch and trigger CI/CD deployment.

Community
Advanced
pkuppenspkuppens

maintenance-cleanup

Clean up merged branches, worktrees, GitHub Actions runs, and tmp directories.

Community
Intermediate
tkerseytkersey
66

fin

Finish GitHub pull requests by updating branches, monitoring CI, and squash-merging.

Community
Advanced