skills.rest
ben-mad-jlp
ben-mad-jlpCOMMUNITY
Explore all skills by this author →
GitHub

finishing-a-development-branch

Guide Git branch completion with merge, PR, cleanup, or keep options.

Updated Jan 12, 2026
Search Tags:#git#workflow#cleanup#merge#branch#pull-request
One-click install
npx skills add https://github.com/ben-mad-jlp/claude-mermaid-collab --skill finishing-a-development-branch-ben-mad-jlp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/ben-mad-jlp/claude-mermaid-collab/tree/main/skills/finishing-a-development-branch
Command: npx skills add https://github.com/ben-mad-jlp/claude-mermaid-collab --skill finishing-a-development-branch-ben-mad-jlp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides teams in finishing a development branch after implementation is complete and all tests pass by presenting deterministic options for merge, PR, cleanup, or keeping the branch for future work.

Core Features & Use Cases

  • Structured decision options: Verifies tests pass and provides a fixed set of actions to resolve the branch.
  • Branch lifecycle guidance: Supports local merge, PR creation, keeping the branch for later work, or discarding the work with safeguards.
  • Operational flow: Includes base-branch detection, standard git workflows, and optional worktree cleanup.

Quick Start

Run the finishing-a-development-branch skill during a completed feature cycle to select one of the four options and execute the corresponding commands.

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 git feature branch after tests pass?▼

Finishing a development branch involves choosing one of four deterministic actions: local merge, pull request creation, branch cleanup, or keeping the branch. The workflow automatically detects the base branch and executes the selected option with optional worktree cleanup.

What's the best way to clean up a git branch after merging?▼

Cleaning up a git branch after merging requires selecting the cleanup option in this workflow, which executes structured verification and base-branch detection steps before performing optional worktree removal to ensure a deterministic local repository state.

Can I create a pull request directly from a local git workflow?▼

You can create a pull request from a local git workflow by selecting the PR creation option, which is one of the four explicit deterministic choices provided after verifying that all implementation and tests are complete.

Does this branch finishing workflow support bugfix and maintenance branches?▼

This branch finishing workflow supports bugfix and maintenance branches alongside feature branches. It is applicable to any Git-based workflow where you need to decide how to merge, PR, or clean up after implementation and tests pass.

When should I keep a development branch instead of merging or deleting it?▼

You should keep a development branch when future work is required. The workflow offers an explicit option to retain the branch for later development, bypassing the merge, PR, and cleanup actions while ensuring the current state is preserved.

Related Skills

Explore More Software Engineering Skills→
WesleyMFrederickWesleyMFrederick

setting-up-implementation-worktree

Create a fresh git worktree with verified tests and dependencies.

Community
Advanced
dceoydceoy
2

clean-gone-branches

Remove git branches marked as 'gone' and their worktrees from a local repository.

Community
Basic
nicograefnicograef
2

finish-branch

Run tests and merge, pull request, or delete completed Git branches.

Community
Advanced
the-agency-aithe-agency-ai
39

Post-Merge

Verify merged pull requests, merge origin updates, and create GitHub releases.

Official
Advanced