finishing-a-development-branch

Present four deterministic Git branch finishing options and clean up worktrees.

1|Updated Nov 22, 2025
One-click install
npx skills add https://github.com/gmliao/swift-state-tree --skill finishing-a-development-branch-gmliao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/gmliao/swift-state-tree/tree/main/.agent/skills/Superpowers/finishing-a-development-branch
Command: npx skills add https://github.com/gmliao/swift-state-tree --skill finishing-a-development-branch-gmliao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides teams to finish development branches by presenting deterministic options for merge, PR, or cleanup, ensuring a clean and auditable conclusion to worked-on features.

Core Features & Use Cases

  • Present exactly four options to finalize the branch:
    1. Merge the feature branch locally to the base branch
    2. Push and create a Pull Request
    3. Keep the branch as-is for later review
    4. Discard the work and clean up
  • Automates base-branch determination and post-action cleanup
  • Supports safe, auditable workflows with explicit confirmations and cleanups

Quick Start

Process a finished development branch by verifying tests, determining the base branch, presenting the four options, executing the chosen action, and cleaning up the worktree.

Frequently Asked Questions about finishing-a-development-branch

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

FAQPage Schema
How do I finish a development branch and choose between merging or creating a pull request?

Finishing a development branch involves selecting one of four options: merge locally to the base branch, push and create a pull request, keep the branch as-is, or discard the work. This enforces a clean and auditable workflow.

What is the best way to clean up a git worktree after merging a feature branch?

Cleaning up a git worktree after merging is handled automatically by finalizing the branch with a structured workflow. Once you select an action like merge or discard, the tool automatically cleans up the worktree afterward.

How does base branch detection work when finalizing a git feature branch?

Base branch detection works by automatically identifying the originating branch during the finalization process. This ensures the merge or pull request targets the correct parent branch without requiring manual input.

Can I discard git development work and safely remove the branch?

Yes, you can discard development work and safely remove the branch by choosing the discard and clean up option. This action removes the unwanted feature and automatically cleans up the associated worktree.

Do I need passing tests before finalizing a development branch?

Yes, you need passing tests before finalizing a development branch. The workflow applies when implementation is complete and tests pass, ensuring only verified code proceeds to merge, pull request, or review.