finishing-a-development-branch

Finalize a development branch with merge, PR, or cleanup options.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Sjw2005/https---gitee.com-song-jiawei-2005-yolopro --skill finishing-a-development-branch-sjw2005
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/Sjw2005/https---gitee.com-song-jiawei-2005-yolopro/tree/main/.agents/skills/finishing-a-development-branch
Command: npx skills add https://github.com/Sjw2005/https---gitee.com-song-jiawei-2005-yolopro --skill finishing-a-development-branch-sjw2005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides the finalization of development work by providing structured, decision-ready options for merging, PR creation, or cleanup once tests pass.

Core Features & Use Cases

  • Verifies tests pass before proceeding with merge or PR.
  • Determines the appropriate base branch and presents four explicit options.
  • Automates or guides post-merge cleanup and worktree handling in typical workflows.

Quick Start

Use this skill to finalize a development branch by confirming test results and choosing a merge path.

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 finalize a development branch after tests pass?

To finalize a development branch after tests pass, you determine the base branch and select from four explicit options for deterministic merging, pull request creation, or cleanup to complete the workflow.

What is the best way to structure a git workflow for branch cleanup and merging?

A structured git workflow for branch cleanup enforces an end-to-end process: it verifies tests, determines the base branch, presents merge options, and handles optional worktree cleanup automatically.

Can I automate worktree cleanup during a pull request workflow?

Yes, you can automate worktree cleanup during a pull request workflow by selecting an explicit finalization option that handles post-merge worktree handling once test verification succeeds.

Does this branch management process require a specific merge strategy?

This branch management process does not enforce one merge strategy; instead, it presents a deterministic four-option decision set, allowing you to choose the appropriate merge or PR path.

What happens if test verification fails before a branch merge?

If test verification fails, the branch merge process halts, as the structured workflow strictly requires implementation to be complete and tests to pass before presenting finalization options.