finishing-a-development-branch

Automate Git branch finalization with merge, PR, or cleanup options.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/Phife726/ds_agent --skill finishing-a-development-branch-phife726
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/Phife726/ds_agent/tree/main/finishing-a-development-branch
Command: npx skills add https://github.com/Phife726/ds_agent --skill finishing-a-development-branch-phife726

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finishing a development branch requires disciplined decision-making to ensure code quality and clean repository state, guiding users through verification and post-workflow choices.

Core Features & Use Cases

  • Verifies tests before completion to prevent introducing failures.
  • Presents explicit options for how to finalize work: merge locally, push and create a PR, keep the branch as-is, or discard.
  • Handles base-branch detection and optional cleanup of the worktree to maintain a clean repository state.

Quick Start

Verify tests pass, choose an option, and let the system perform the corresponding merge or cleanup actions.

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 finalize a git development branch with a structured merge or cleanup?

To finalize a git development branch, this Skill verifies tests pass, detects the base branch, and presents exactly four options: merge locally, push and create a pull request, keep the branch as-is, or discard the work entirely.

Can I create a pull request after verifying tests on a feature branch?

Yes, you can create a pull request after verifying tests. The Skill presents an explicit option to push your feature branch and initiate a PR, ensuring code quality checks pass before finalizing the workflow.

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

The best way to clean up git worktrees after merging is to let the Skill handle post-worktree cleanup automatically. Once you select a merge or discard action, it executes the choice and removes the associated worktree to maintain repository hygiene.

How does base branch detection work when finishing a feature branch?

Base branch detection works by automatically identifying the target branch for your merge or pull request. The Skill evaluates your current git workflow state to determine the correct base branch before presenting finalization options.

What should I do if I want to keep my branch as-is instead of merging or discarding?

If you want to keep your branch as-is, simply select the explicit option to retain the branch. The Skill will finalize the workflow without performing a local merge, pull request, or worktree cleanup, preserving your current repository state.