finishing-a-development-branch

Validate tests and present merge, PR, keep, or discard options for a development branch.

2|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/JaimeJunr/context-mode --skill finishing-a-development-branch-jaimejunr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/JaimeJunr/context-mode/tree/main/.claude/skills/finishing-a-development-branch
Command: npx skills add https://github.com/JaimeJunr/context-mode --skill finishing-a-development-branch-jaimejunr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates finishing a development branch by validating tests and presenting structured completion options.

Core Features & Use Cases

  • Verify tests
  • Determine base branch
  • Present four options
  • Execute chosen option
  • Cleanup worktree

Quick Start

Verify tests pass, determine the base branch, present the four options, execute the chosen option, and clean up the worktree.

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 finish a git development branch and merge it back safely?

To finish a git development branch, you must verify tests pass, determine the base branch, select one of four explicit completion options, execute the chosen path, and clean up the worktree.

What are the options for merging a completed feature branch?

The four explicit options for merging a completed feature branch are executing a direct merge, creating a pull request, keeping the branch, or discarding the work entirely.

How do I verify tests before merging a git worktree?

The skill enforces test verification before any merge actions by validating tests automatically, preventing execution of completion options until all tests pass successfully.

Does this branch management workflow require a specific git worktree setup?

The workflow is applied to software projects with feature branches and handles worktree cleanup automatically, but the metadata indicates no specific external dependencies are required to execute the process.

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

The best way to clean up a git worktree after merging is to let the skill manage the cleanup automatically, executing the chosen completion path while ensuring the worktree is removed properly.