skills.rest
jacexh
jacexhCOMMUNITY
Explore all skills by this author →
GitHub

finishing-a-development-branch

Verify tests and execute merge, PR, preserve, or discard workflows for a development branch.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finishing-a-development-branch helps developers decide and safely execute the final integration step for completed feature branches, preventing accidental merges of failing code and accidental deletion of work. It enforces test verification, explicit confirmations for destructive actions, and clear options for merging, creating a PR, preserving, or discarding work.

Core Features & Use Cases

  • Test verification: Run and require passing test suites before offering integration choices.
  • Structured options: Present exactly four concise actions (merge locally, push+create PR, keep branch, discard with confirmation).
  • Execution and cleanup: Perform merges or pushes, create PRs, and optionally remove git worktrees while requiring typed confirmation before destructive operations.
  • Use case: Finalizing a completed feature branch after implementation and local testing, choosing whether to merge, open a PR, preserve work, or discard changes safely.

Quick Start

Use the finishing-a-development-branch skill to verify tests and present the four integration options for the current feature branch.

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 safely merge a finished git feature branch into the main repository?▼

Safely merging a finished git feature branch requires verifying passing tests first, determining the correct base branch, executing the local merge, and then managing git worktree cleanup with explicit confirmation.

What should I do before opening a pull request for my development branch?▼

Before opening a pull request for your development branch, you must run and pass your test suite. The workflow then pushes the verified branch and creates the PR while preserving local work.

How do I clean up a git worktree after merging a feature branch?▼

Cleaning up a git worktree after merging a feature branch involves selecting the cleanup option during the finalization workflow, which requires typed confirmation before removing the worktree.

Can I preserve my git branch instead of discarding it after tests pass?▼

Yes, you can preserve your git branch. After test verification passes, the workflow presents four structured options including keeping the branch, allowing you to retain the work without merging or discarding it.

What is the best way to discard git branch changes without accidental data loss?▼

The best way to discard git branch changes without accidental data loss is using a workflow that requires typed confirmation before destructive operations, preventing accidental deletion of work.

Related Skills

Explore More Software Engineering Skills→
nassimbfnassimbf
3

using-git-worktrees

Create isolated git worktrees for feature development with safety verification.

Community
Advanced
mdmagnuson-creatormdmagnuson-creator

merge-conflicts

Merge target branches into source branches and resolve pull request conflicts.

Community
Advanced
8b-is8b-is

git-worktree

Create, list, switch, and clean up Git worktrees with a shell script.

Official
Basic
JacobPEvansJacobPEvans
3

rebase-pr

Rebase pull requests onto main with signed commits and GitHub API checks.

Community
Advanced