skills.rest
alo-exp
alo-expOFFICIAL
Explore all skills by this author →
WebsiteGitHub

finishing-branch

Finalize Git branches by verifying tests, choosing merge strategies, and creating PRs.

6|3|Updated Mar 31, 2026
Search Tags:#git-workflow#pull-request#merge-strategy#development-branch#finishing
One-click install
npx skills add https://github.com/alo-exp/silver-bullet --skill finishing-branch-alo-exp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-branch
Source: https://github.com/alo-exp/silver-bullet/tree/main/forge/skills/finishing-branch
Command: npx skills add https://github.com/alo-exp/silver-bullet --skill finishing-branch-alo-exp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides teams through the finalization of development branches, ensuring consistent merge decisions, cleanup, and PR documentation.

Core Features & Use Cases

  • Step 1: Verify completeness (tests pass, reviews addressed, verification document updated).
  • Step 2: Choose a merge strategy (squash, merge commit, or rebase + merge) and apply consistently.
  • Step 3: Update branch (rebase on latest main, resolve conflicts, run tests).
  • Step 4: Create PR (title and body conventions, reviewers, linked issues).
  • Step 5: Document decisions and clean up locally and remotely after merge.
  • Step 6: Exit condition when PR is merged or branch is cleaned up.

Quick Start

Run through the checklist to finalize a branch by verifying tests and reviews, selecting a merge strategy, updating the branch, creating a PR, and documenting decisions.

Frequently Asked Questions about finishing-branch

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

FAQPage Schema
How do I finalize a development branch with a clean pull request?▼

To finalize a development branch with a clean pull request, you must verify tests pass, address reviews, update verification docs, rebase on main, and consistently apply a chosen merge strategy like squash or merge commit before creating the PR.

What is the best merge strategy for finishing a feature branch?▼

The best merge strategy for finishing a feature branch depends on your workflow, but standard options include squash, merge commit, or rebase plus merge to ensure a clean, standardized project history during PR finalization.

How do I clean up local and remote git branches after a merge?▼

To clean up local and remote git branches after a merge, document the final merge decisions and explicitly remove the development branch both locally and remotely to maintain a tidy repository state.

What should be included in a pull request for a release branch?▼

A pull request for a release branch should include standardized title and body conventions, assigned reviewers, linked issues, and verification documents proving that tests pass and code reviews are addressed.

Do I need to rebase my feature branch before creating a pull request?▼

Yes, you need to rebase your feature branch on the latest main branch before creating a pull request to resolve conflicts early, verify tests pass against the current codebase, and ensure a smooth merge.

Why does branch finalization require verification documents?▼

Branch finalization requires verification documents to enforce completion criteria, providing a standardized record that tests pass and code reviews are addressed before the development branch is merged and cleaned up.

Related Skills

Explore More Software Engineering Skills→
Tx1207Tx1207
5

project-creator

Create a new project from a template, initialize uv, and configure a local Git repository.

Community
Advanced
JacobPEvansJacobPEvans
3

refresh-repo

Synchronize a local Git repository and check open Pull Requests for merge readiness.

Community
Intermediate
motlinmotlin
14

git-workflow

Standardize git commits, rebasing, conflict resolution, and branch management.

Community
Basic
julianobarbosajulianobarbosa
7

obsidian (obsidian-skill)

Resolve complex Git history issues with rebase, cherry-pick, bisect, worktrees, and reflog.

Community
Advanced