merged

Delete merged branches and worktrees with approval, then update the base branch.

1|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/devbasex/ai-plugins --skill merged-devbasex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merged
Source: https://github.com/devbasex/ai-plugins/tree/main/plugins/ndf/skills/merged
Command: npx skills add https://github.com/devbasex/ai-plugins --skill merged-devbasex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a pull request is merged, leftover feature branches, stale worktrees, and forgotten open issues clutter the repository and mislead the next developer. This Skill automates the entire post-merge cleanup so nothing is left behind. ## Core Features & Use Cases - Post-merge cleanup: Verify the PR is merged, remove its worktree and branch, update the base branch, and restore any stashed changes. - Bulk merged-branch cleanup: List all branches already merged into the base branch and delete them locally and remotely, with explicit approval before each destructive step. - Base branch integration: Merge the latest base branch into an in-progress feature branch, reporting conflicts without auto-resolving them. - Issue closing: Parse the merged PR body for closing keywords (Fixes, Closes, Resolves) and close any still-OPEN issues, including cross-repository references. - Use Case: After merging PR #123, run the cleanup to delete its worktree and branch, tidy other merged branches, close the linked issue, and get a completion report with stage-check output. ## Quick Start Ask the assistant to clean up after merged PR 123 by deleting its branch and worktree, tidying other merged branches, and closing its linked issues.

Frequently Asked Questions about merged

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

FAQPage Schema
How do I delete merged git branches after a pull request?▼

Fetch the base branch, list merged branches with git branch --merged origin/<base>, then delete them with git branch -d. This Skill automates the flow and requires your approval on the listed targets before deleting anything locally or remotely.

How to clean up git worktrees after merging a PR?▼

Locate the worktree with git worktree list, then remove it with git worktree remove <path>. The Skill shows each worktree path and its uncommitted-change status first, and only deletes after you approve.

Why didn't GitHub auto-close my issue after merging?▼

GitHub only auto-closes issues when merging into the default branch. If your base branch differs, closing keywords like Fixes #123 are ignored, so the Skill parses the PR body and closes still-OPEN issues manually via gh issue close.

Can I update my feature branch with the latest base branch?▼

Yes. The Skill fetches origin/<base> and merges it into your current branch with --no-edit, stashing uncommitted changes first. On conflict it lists the conflicting files and stops instead of auto-resolving.

Is it safe to run automated branch deletion?▼

The Skill never deletes without consent. Worktree, local branch, and remote branch deletions each require separate approval with the exact targets listed, and remote deletion is confirmed independently since it affects shared branches.