finishing-a-development-branch

Merging a development branch involves verifying tests pass, selecting your merge strategy—locally, via pull request, or keeping the branch as-is—then executing that choice. This Skill automates test verification and presents all four options, letting you choose the integration method that fits your workflow before cleanup.

A structured merge process ensures tests pass first, then offers explicit options: merge locally to main, push and create a pull request for review, keep the branch for later, or discard it. This prevents broken merges and gives you control over integration timing and visibility.

Branch cleanup removes feature branches and associated Git worktrees after integration. This Skill automates cleanup as part of the completion workflow, so you don't manually track which branches to remove after merging or pushing your changes.

Yes. This Skill offers a push-and-create-PR option that skips local merging entirely. You choose to push your branch and create a pull request for code review before any integration, keeping your branch separate until approval.

Test verification is mandatory before any completion option appears. If tests fail, the Skill stops and prevents you from merging, pushing, or discarding until tests pass, ensuring only verified code enters the main codebase.

Local merge integrates immediately without review; pull request adds a review gate before integration. This Skill presents both explicitly so you choose based on your team's approval process, code review needs, and whether work should be visible before merging.