skills.rest
ederheisler
ederheislerCOMMUNITY
Explore all skills by this author →
GitHub

finishing-a-development-branch

Verify tests and present merge, pull request, keep, or discard options for a development branch.

Updated Aug 27, 2026
Search Tags:#git#development#worktree#merge#branch-management#pull-request#finish
One-click install
npx skills add https://github.com/ederheisler/agent-skills --skill finishing-a-development-branch-ederheisler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/ederheisler/agent-skills/tree/main/skills/finishing-a-development-branch
Command: npx skills add https://github.com/ederheisler/agent-skills --skill finishing-a-development-branch-ederheisler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams finishing development work often struggle to decide how to integrate, test, and clean up a finished feature branch. This guide provides a deterministic path to choose between merge, PR, or cleanup while preserving tests and history.

Core Features & Use Cases

  • Verify tests pass before exposing merge options.
  • Determine the correct base branch for the merge.
  • Present exactly four actions: Merge back to the base branch locally, Push and create a Pull Request, Keep the branch as-is (worktree preserved), or Discard this work.
  • Automate cleanups of worktrees and branches after the chosen action.

Quick Start

Run this skill to finalize a feature branch by selecting one of four structured options after tests pass.

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 finishing a feature?▼

To finalize a git development branch, you can choose between merging it back to the base branch, pushing it to create a pull request, keeping it preserved, or discarding the work entirely.

What is the best way to choose between merging or creating a pull request for a finished branch?▼

The best way to choose between merging or a pull request is using a structured workflow that verifies tests pass first, then presents exactly four deterministic actions to integrate, preserve, or discard the branch.

Does this branch finalization process verify tests before allowing a merge?▼

Yes, this branch finalization process enforces test verification as a safeguard before exposing any merge or cleanup options, ensuring completed work is validated before integration.

Can I discard development work and clean up the git worktree automatically?▼

Yes, you can discard development work and trigger automated cleanup of git worktrees and branches by selecting the discard action from the four presented finalization options.

How do I determine the correct base branch when merging a completed feature branch?▼

Determining the correct base branch for merging a completed feature branch is automated by the workflow, which identifies the appropriate target before presenting local merge or pull request options.

Related Skills

Explore More Software Engineering Skills→
wsxwj123wsxwj123
7

finishing-a-development-branch

Coordinate merge, PR, or cleanup decisions after tests pass.

Community
Intermediate
rishikanthcrishikanthc

finishing-a-development-branch

Verify tests and guide git branch merge, push, preserve, or discard decisions.

Community
Intermediate
Benja-PaulsBenja-Pauls
2

git-workflow

Enforce Git branch naming, commit message, and pull request conventions.

Community
Basic
falconntfalconnt
3

finishing-branch

Finalize Git feature branches with test verification and structured merge options.

Community
Basic