finishing-a-development-branch

Verify tests and choose merge or cleanup for finished development branches.

28|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/bidah/react-native-hifi --skill finishing-a-development-branch-bidah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/bidah/react-native-hifi/tree/main/skills/finishing-a-development-branch
Command: npx skills add https://github.com/bidah/react-native-hifi --skill finishing-a-development-branch-bidah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents ad hoc, unverified branch completions by verifying tests, defining explicit next actions, and enforcing cleanup before the work is considered finished.

Core Features & Use Cases

  • Test-first validation: Enforces running the relevant test suite and halting progress if failures are detected, ensuring no broken code is promoted.
  • Structured completion options: Presents exactly four concise choices—merge locally, push with a PR, keep the branch, or discard—so stakeholders can quickly decide the desired outcome.
  • Worktree and branch hygiene: Handles base branch detection, optional confirmation for destructive choices, and precise cleanup for merged or discarded worktrees.

Quick Start

Ask the agent to use finishing-a-development-branch to verify tests, select the right completion option, and tidy up the worktree accordingly.

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 finish a git development branch after implementation is complete?

To safely finish a git development branch, you must first verify your test suite passes and then choose a structured completion path: merge locally, push with a pull request, keep, or discard the branch.

What is the best way to clean up a git worktree after merging a branch?

The best way to clean up a git worktree after merging involves selecting a structured completion option that triggers precise cleanup procedures for the merged worktree, ensuring no residual files remain.

How do I prevent merging unverified or broken code from a feature branch?

Prevent merging broken code from a feature branch by using a workflow that enforces test-first validation, halting branch completion progress automatically if any test failures are detected.

What should I do with my local git branch: merge, create a pull request, or discard?

Deciding whether to merge locally, create a pull request, keep, or discard a local git branch depends on team needs, and structured prompts can guide stakeholders through these exact four choices.

Does finishing a development branch require checking the base branch before merging?

Yes, finishing a development branch requires base branch detection to ensure your changes are evaluated against the correct upstream source before any merge or cleanup routines are executed.

Why do I need to verify tests before discarding a git branch?

Verifying tests before discarding a git branch prevents accidental loss of functional code by ensuring the branch is truly redundant, with optional confirmation prompted for destructive choices.