remove-feature

Remove feature branches, GitHub pull requests, and local git worktrees.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Vulnetix/vdb-api --skill remove-feature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: remove-feature
Source: https://github.com/Vulnetix/vdb-api/tree/main/.claude/skills/remove-feature
Command: npx skills add https://github.com/Vulnetix/vdb-api --skill remove-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill automates the tedious and error-prone process of cleaning up after a feature development cycle, ensuring all related branches, PRs, and local worktrees are removed.

Core Features & Use Cases

  • Comprehensive Cleanup: Closes GitHub PRs, deletes local and remote branches, and removes associated git worktrees.
  • Inverse of new-feature: Designed to perfectly complement the feature creation process.
  • Use Case: After merging a feature branch and completing its development, use this skill to automatically remove the branch, close the PR, and delete the worktree, keeping your repository tidy.

Quick Start

Use the remove-feature skill to clean up after the feature branch associated with PR number 123.

Frequently Asked Questions about remove-feature

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

FAQPage Schema
How do I clean up git worktrees and remote branches after a PR is merged?

To clean up git worktrees and remote branches after a PR is merged, you need to remove the feature branch, close the associated GitHub pull request, and delete the local worktree. This ensures all artifacts of a completed feature are fully deleted.

Can I close a GitHub pull request and delete the source branch automatically?

Yes, you can close a GitHub pull request and delete the source branch automatically by providing the PR number. The cleanup process handles both the PR closure and the removal of associated local and remote branches.

What happens if I try to delete a git branch that has already been removed?

If you try to delete a git branch that has already been removed, the system validates branch existence and gracefully handles already-deleted resources. This prevents errors during the cleanup of abandoned features or previously merged branches.

Does branch cleanup work with both PR numbers and branch names as inputs?

Yes, branch cleanup works with both PR numbers and branch names as inputs. This allows you to target the exact feature you want to remove, ensuring the correct pull request, remote branch, and local git worktree are deleted.

What is the best way to remove abandoned feature branches and their associated PRs?

The best way to remove abandoned feature branches and their associated PRs is to perform a comprehensive cleanup that deletes local and remote branches, closes GitHub PRs, and removes linked git worktrees, keeping your repository tidy without manual errors.