skills.rest
xianmingyao
xianmingyaoCOMMUNITY
Explore all skills by this author →
GitHub

finishing-a-development-branch

Validate tests and select merge, PR, keep, or cleanup for a Git branch.

1|1|Updated Mar 18, 2026
Search Tags:#git#development#cleanup#workflow-automation#branch-management#merge-strategy
One-click install
npx skills add https://github.com/xianmingyao/openclaw-CaySon --skill finishing-a-development-branch-xianmingyao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/xianmingyao/openclaw-CaySon/tree/main/.agent/skills/finishing-a-development-branch
Command: npx skills add https://github.com/xianmingyao/openclaw-CaySon --skill finishing-a-development-branch-xianmingyao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finishing a development branch helps teams finalize work after implementation and testing by offering a structured decision path for merging, PR creation, or cleanup.

Core Features & Use Cases

  • Verify tests pass before proceeding with integration.
  • Determine the appropriate base branch for merging.
  • Present exactly four options to the user: merge locally, push and create a PR, keep the branch as-is, or discard the work.
  • Execute the chosen option and perform optional cleanup of the worktree after completion.
  • Use in standard feature-branch workflows to accelerate safe, auditable merges.

Quick Start

Verify tests pass, determine the base branch, and choose one of four options to merge, PR, keep, or discard, with automatic worktree 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 automate finalizing a Git development branch after testing?▼

Finalizing a Git development branch is automated by validating tests, detecting the base branch, and presenting four explicit options: merge locally, push and create a PR, keep the branch, or discard the work.

What are the standard options for integrating a completed feature branch?▼

The standard options for integrating a completed feature branch are merging locally, pushing to create a PR, keeping the branch as-is, or discarding the work entirely.

How do I ensure tests pass before merging a feature branch?▼

To ensure tests pass before merging a feature branch, the finalization workflow validates test results first and only proceeds to base-branch detection and integration options if the tests pass.

Does branch finalization support automatic worktree cleanup in CI pipelines?▼

Branch finalization supports CI-enabled pipelines by executing the chosen integration option and performing optional worktree cleanup automatically after completion.

What is the best way to discard a completed development branch locally?▼

Discarding a completed development branch is handled by selecting the discard option during the finalization workflow, which also triggers optional worktree cleanup.

When should I use a PR instead of a local merge for my feature branch?▼

You should use a PR instead of a local merge when your feature is complete and ready for integration but requires auditable review through a push, rather than direct local merging to the base branch.

Related Skills

Explore More Software Engineering Skills→
greglambgreglamb
1

using-git-worktrees

Create an isolated Git worktree for feature development without disrupting the current workspace.

Community
Intermediate
tachiiri-orgtachiiri-org

release

Create a pull request from the dev branch to main after verifying branch and remote state.

Official
Intermediate
AhmedElhadareyAhmedElhadarey
2

finishing-a-development-branch

Verify tests and select merge, PR, keep, or discard for a feature branch.

Community
Advanced
UniClipboardUniClipboard
1.5k

finishing-a-development-branch

Offer merge, PR, keep, or discard options after tests pass.

Official
Advanced