finishing-a-development-branch

Verify tests and guide branch integration or cleanup decisions.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/greglamb/macos-name-tag-app --skill finishing-a-development-branch-greglamb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/greglamb/macos-name-tag-app/tree/main/.claude/skills/finishing-a-development-branch
Command: npx skills add https://github.com/greglamb/macos-name-tag-app --skill finishing-a-development-branch-greglamb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined way to finish completed development work without skipping test verification, making unclear integration decisions, or accidentally deleting valuable changes.

Core Features & Use Cases

  • Test Verification: Confirm that the project's test suite passes before proceeding.
  • Integration Choices: Present structured options to merge locally, create a pull request, keep the branch, or discard the work.
  • Safe Cleanup: Handle branch and worktree cleanup only when appropriate, with explicit confirmation required before discarding changes.
  • Use Case: After completing a feature on a development branch, use this Skill to verify tests, identify the base branch, choose an integration path, and preserve or clean up the worktree safely.

Quick Start

Use the finishing-a-development-branch skill to verify the completed work and guide me through merging, creating a pull request, preserving, or discarding the 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 finish a git development branch without losing uncommitted changes?

Finishing a development branch safely requires running test verification, detecting the base branch, and selecting from four structured workflow options including local merge or pull request creation. Typed confirmation is required before any destructive discard operations to prevent data loss.

What steps are involved in a git merge workflow after completing a feature?

A git merge workflow involves verifying the test suite passes, detecting the base branch, and choosing to merge locally, create a pull request, preserve the branch, or discard the work. Safe cleanup of branches and worktrees follows only when explicitly appropriate.

Can I create a pull request after verifying tests on my local development branch?

Yes, creating a pull request is one of four structured integration options available after test verification passes and the base branch is detected. The workflow guides you through pull request creation as an alternative to local merging, preserving, or discarding the branch.

What is the best way to handle git worktree cleanup after merging a branch?

Git worktree cleanup should be handled only after successfully integrating the branch. The workflow ensures safe cleanup by performing branch and worktree management exclusively when appropriate, protecting valuable changes until integration is fully complete.

Does test verification need to pass before a local merge or branch discard?

Yes, test verification must pass before proceeding with any integration or branch discard. The workflow requires the project's test suite to succeed first, ensuring completed implementation work is validated before guiding local merge, pull request, preservation, or discard decisions.