skills.rest
isaenter
isaenterCOMMUNITY
Explore all skills by this author →
GitHub

finish-branch

Automate post-kaizen branch finalization with merge, PR, keep, or discard decisions.

Updated Aug 23, 2026
Search Tags:#code-review#kaizen#branch-management#git-workflow#pull-request#branch-cleanup
One-click install
npx skills add https://github.com/isaenter/UES-PRO --skill finish-branch-isaenter
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finish-branch
Source: https://github.com/isaenter/UES-PRO/tree/main/frontend-vben/.claude/skills/finish-branch
Command: npx skills add https://github.com/isaenter/UES-PRO --skill finish-branch-isaenter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow guides the finalization of a development branch after kaizen and before delivery, reducing manual coordination and ensuring consistent handoffs.

Core Features & Use Cases

  • Branch lifecycle decisions: choose between merge, create PR, keep branch, or discard with built-in safeguards.
  • Automatic PR description: when PR is chosen, generates a PR description from related design, quality, and plan documents.
  • Safe merge & cleanup: checks for conflicts before merging and handles branch deletion with user confirmation.
  • Use Case: When a feature branch has completed kaizen, use this to finalize the branch and prepare for delivery with minimal risk.

Quick Start

Run the finish-branch workflow to select an action (merge, pr, keep, or discard) and let the system guide the next steps.

Frequently Asked Questions about finish-branch

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

FAQPage Schema
How do I finalize a Git branch after kaizen and prepare it for delivery?▼

To finalize a Git branch after kaizen, you can run a branch finalization workflow that guides post-kaizen delivery actions, automatically checking for merge conflicts and preparing the branch for handoff.

Can I automatically generate a pull request description from existing project documents?▼

Yes, when you choose to create a pull request during branch finalization, the system automatically generates a PR description by extracting details from related design, quality, and plan documents.

What is the best way to decide whether to merge, keep, or discard a feature branch?▼

The best way to decide on a feature branch's lifecycle is to use a deterministic decision flow that evaluates your branch state and guides you to safely merge, create a PR, keep, or discard it.

How does branch cleanup work when discarding a Git branch during finalization?▼

Branch cleanup during finalization handles branch deletion with a user confirmation prompt, ensuring safe removal of the Git branch only after you explicitly approve the discard action.

Does the merge process check for Git conflicts before finalizing the branch?▼

Yes, the merge process checks for Git conflicts during branch finalization to ensure safe merges, preventing problematic integrations before you proceed with delivery or branch cleanup.

Related Skills

Explore More Software Engineering Skills→
m-xlseam-xlsea
319

finish-branch

Finalize Git feature branches with merge, PR, keep, or discard options.

Community
Advanced
GitnappGitnapp

github-pr-workflow

Automate GitHub pull request lifecycle from branch creation to merge.

Community
Advanced
aporto-techaporto-tech

Ship

Automate code shipping with branch merging, tests, version bumps, commits, and pull requests.

Official
Advanced
GaryOcean428GaryOcean428

finishing-a-development-branch

Verify project tests and present Git integration options for branch completion.

Community
Intermediate