issue-complete

Remove worktrees, ports, branches, and databases after merging a pull request.

2|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/elijahmurray/vandra-dev --skill issue-complete
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-complete
Source: https://github.com/elijahmurray/vandra-dev/tree/main/skills/issue-complete
Command: npx skills add https://github.com/elijahmurray/vandra-dev --skill issue-complete

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the cleanup process after a pull request has been merged, ensuring that development environments remain tidy and resources are freed up.

Core Features & Use Cases

  • Worktree Removal: Deletes the isolated worktree associated with the completed issue or PR.
  • Port Release: Frees up any network ports that were allocated to the worktree.
  • Branch Deletion: Removes the feature branch from the local repository.
  • Database Cleanup: Drops the isolated database instance created for the worktree.
  • Use Case: After successfully merging a new feature into the main branch, use this Skill to automatically remove the temporary worktree, its associated database, and the feature branch, keeping your development environment clean.

Quick Start

Run the command to clean up after merging a pull request.

Frequently Asked Questions about issue-complete

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

FAQPage Schema
How do I clean up local branches after a pull request is merged?

Cleaning up local branches after a merged pull request involves removing the feature branch from the local repository while also deleting associated worktrees, releasing allocated ports, and dropping databases to prevent resource conflicts.

What is the best way to automate git worktree removal after feature integration?

Automating git worktree removal after feature integration involves deleting the isolated worktree, freeing network ports, and dropping associated databases. This prevents orphaned resources and maintains an efficient development workflow post-merge.

How do I drop an isolated database after merging a feature branch?

To drop an isolated database after merging a feature branch, you must automate the cleanup process to remove the database instance created for the worktree. This frees up resources and keeps your development environment tidy.

Does automated PR cleanup release allocated network ports?

Yes, automated PR cleanup releases allocated network ports by removing the isolated worktree associated with the completed issue. This prevents potential conflicts and ensures no orphaned resources are left behind.

When should I run a development environment cleanup script?

You should run a development environment cleanup script immediately after successfully merging a new feature into the main branch. This ensures temporary worktrees, associated databases, and feature branches are removed without causing conflicts.

Why do I need to remove orphaned resources after a pull request?

You need to remove orphaned resources after a pull request to prevent potential conflicts and resource wastage in your development workflow. Leaving worktrees, ports, and databases active leads to environmental clutter and inefficiency.