finishing-a-development-branch

Verify tests and present four integration options for finishing a development branch.

66|20|Updated Dec 30, 2025

Search Tags:#git #workflow #merge #pull-request #tests #development-branch #finishing

Ready to run

npx skills add https://github.com/cooker/wxHm --skill finishing-a-development-branch-cooker

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/cooker/wxHm/tree/main/.cursor/skills/finishing-a-development-branch
Command: npx skills add https://github.com/cooker/wxHm --skill finishing-a-development-branch-cooker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finishing a development branch ensures code changes are integrated safely by verifying tests and choosing a clear path for merging, PR creation, or cleanup.

Core Features & Use Cases

Verify tests pass before finalizing the branch.
Present four explicit options: merge locally, push and create a PR, keep the branch as-is, or discard.
Clean up worktrees and branches according to the chosen path to maintain repository hygiene.

Quick Start

After development is complete and tests pass, run this skill to guide the finalization process and select the appropriate integration path (merge, PR, keep, or discard).

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 after passing tests?▼

To finalize a git development branch after tests pass, you determine the base branch and select one of four integration paths: merge locally, push and create a pull request, keep the branch, or discard it. The workflow then performs cleanup based on your selection.

What is the best way to merge a completed development branch in a multi-branch workflow?▼

The best way to merge a completed development branch in a multi-branch workflow is to verify tests, determine the correct base branch, and choose between creating a local merge, opening a pull request, keeping the branch, or discarding changes, followed by worktree cleanup.

Does finishing a development branch require local test verification before creating a pull request?▼

Yes, finishing a development branch requires local test verification before proceeding to create a pull request or merging. Ensuring tests pass is the mandatory first step before the four integration options are presented for selection.

Can I discard changes and clean up worktrees when finishing a development branch?▼

Yes, you can discard changes and clean up worktrees when finishing a development branch. Discarding is one of the four explicit options provided, automatically handling branch and worktree cleanup to maintain repository hygiene.

What options do I have for integrating a development branch besides a local merge?▼

Besides a local merge, options for integrating a development branch include pushing to create a pull request, keeping the branch as-is for later work, or discarding the branch entirely. All paths include subsequent worktree and branch cleanup.

When should I keep a development branch as-is instead of merging or discarding?▼

You should keep a development branch as-is instead of merging or discarding when development is incomplete or tests fail. This option pauses integration while preserving your work, skipping the final cleanup steps applied to merged or discarded branches.