Radberi-FinishingDevelopmentBranch

Guide feature branch completion through a five-option merge, PR, or cleanup decision flow.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/Shade666/huml-dotnet --skill radberi-finishingdevelopmentbranch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Radberi-FinishingDevelopmentBranch
Source: https://github.com/Shade666/huml-dotnet/tree/main/.claude/skills/Radberi-FinishingDevelopmentBranch
Command: npx skills add https://github.com/Shade666/huml-dotnet --skill radberi-finishingdevelopmentbranch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides completing development work by presenting structured options for merge, PR, or cleanup when a feature branch is ready.

Core Features & Use Cases

  • Verifies tests pass and establishes a clear workflow for integration.
  • Presents five concrete options to decide how to complete a development branch.
  • Helps coordinate merging, PR creation, or cleanup while maintaining safety.

Quick Start

Run the finishing assistant to verify tests and then select one of the five options to complete the work.

Frequently Asked Questions about Radberi-FinishingDevelopmentBranch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I finalize a git feature branch after tests pass?

To finalize a git feature branch after tests pass, you must decide between merging, opening a pull request, or cleanup. This workflow presents five concrete options to execute the branch completion safely.

What is the best way to manage branch merging and cleanup across multiple base branches?

The best way to manage branch merging and cleanup is using a deterministic decision flow that identifies your base branch first. This ensures integration steps remain safe across common base branches before executing merge or cleanup commands.

Can I use a structured workflow to decide between a pull request and a direct merge?

Yes, you can use a structured workflow to decide between a pull request and a direct merge. It detects test outcomes and presents explicit execution steps for five different branch completion options.

How does branch cleanup work when a feature branch is ready for integration?

Branch cleanup works by guiding you through a five-option decision flow once tests pass. It identifies the correct base branch and provides explicit execution steps to safely complete the development work.

When do I need a decision flow for completing development branches?

You need a decision flow for completing development branches when a feature branch has passed testing and requires integration. It helps coordinate merging, pull request creation, or cleanup while maintaining repository safety.