finishing-a-development-branch

Validates tests and presents four options for finishing a Git branch.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/HadiCherkaoui/opencode-config --skill finishing-a-development-branch-hadicherkaoui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/HadiCherkaoui/opencode-config/tree/main/skills/finishing-a-development-branch
Command: npx skills add https://github.com/HadiCherkaoui/opencode-config --skill finishing-a-development-branch-hadicherkaoui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the post-implementation handoff by validating tests and guiding merge or PR decisions.

Core Features & Use Cases

  • Verifies tests pass before proposing integration options.
  • Determines a sensible base branch and suggests concrete actions (merge, PR, or clean-up).
  • Guides safe cleanup and optional worktree handling after the chosen path is executed.

Quick Start

Activate this skill to guide the completion of a development branch by validating tests, presenting four structured options, and performing post-action cleanup.

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 after tests pass?

To finish a git development branch after tests pass, you can streamline the post-implementation handoff by validating test results and selecting from deterministic merge, pull-request, retain, or discard options.

What is the best way to merge a feature branch into main or master?

The best way to merge a feature branch into main or master is to determine a sensible base branch after verifying tests pass, then execute a local merge or create a pull-request with guided post-action cleanup.

Does this workflow support creating a pull request and cleaning up the branch afterwards?

Yes, this workflow supports creating a pull request and cleaning up the branch afterwards by providing local merge or PR creation commands and including post-action cleanup guidance with optional worktree handling.

Why should I verify tests before merging a Git branch?

You should verify tests before merging a Git branch to ensure test verification passes across common bases, which streamlines the post-implementation handoff and validates the decision to merge, PR, retain, or discard.

What are my options for completing a development branch handoff?

Your options for completing a development branch handoff include a four-option choice set that allows you to locally merge, create a pull-request, retain, or discard the branch after tests pass.