finishing-a-development-branch

Finalize a development branch by choosing merge, PR, keep, or discard.

1|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/wedsamuel1230/electronic-mcp-server --skill finishing-a-development-branch-wedsamuel1230
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/wedsamuel1230/electronic-mcp-server/tree/main/.github/skills/finishing-a-development-branch
Command: npx skills add https://github.com/wedsamuel1230/electronic-mcp-server --skill finishing-a-development-branch-wedsamuel1230

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the finalization of a development branch by standardizing how a completed feature is integrated, ensuring tests pass and the team selects a clear path for merge, PR, or cleanup.

Core Features & Use Cases

  • Verify tests and ensure integrity before integration decisions.
  • Present exactly four options: merge locally, push and create PR, keep the branch as-is, or discard the work.
  • Execute or guide the execution of the chosen path, including merge/PR actions and branch cleanup.
  • Real-world use case: After a feature completes and tests pass, use this Skill to decide whether to merge into main, open a PR, preserve the branch for further edits, or discard the work.

Quick Start

Run the finishing-a-development-branch skill after validation tests complete to determine the integration path and apply the chosen option.

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 tests pass?

To finalize a completed development branch, you choose one of four integration paths: merge locally, push and create a pull request, keep the branch as-is, or discard the work, followed by executing the corresponding git commands and cleanup steps.

What are my options for merging a completed git feature branch?

Your options for merging a completed git feature branch are to merge it locally into your main branch, push the branch to a remote repository to open a pull request, keep the branch as-is for further work, or discard the branch entirely.

What is the standard git workflow for branch cleanup after a merge?

The standard git workflow for branch cleanup involves applying a four-option protocol that provides concrete git commands to either merge, open a pull request, keep, or discard the development branch, ensuring standardized finalization and automated removal.

Should I create a pull request or merge my git branch locally?

Whether to create a pull request or merge locally depends on your team's integration needs; this branch finalization process presents both options alongside keeping or discarding the branch, providing the exact git commands needed for your chosen path.

When should I discard a development branch instead of merging it?

You should discard a development branch instead of merging it when the completed work is no longer needed or fails to meet integration requirements, using the standardized git cleanup commands provided by the discard option in the workflow.