finishing-a-development-branch

To finish a development branch, the skill validates that tests pass, detects the common base branch, and presents four deterministic options: merge locally, push a PR, keep the branch, or discard it.

Standard git branch management options for completing a feature include merging locally, pushing a pull request, keeping the branch as-is, or discarding it, with optional worktree cleanup applied post-action.

Yes, you can automate pull request creation after tests pass by selecting the push PR option, which executes the push action and performs optional worktree cleanup as part of the branch finalization process.

Worktree cleanup when finalizing a git branch is an optional post-action step that executes after you choose to merge, push a PR, keep, or discard your development branch, ensuring a controlled cleanup without drift.

You should discard a development branch instead of merging when the completed feature is no longer needed, selecting the discard option from the four deterministic integration choices to safely finalize the work.

Finishing a development branch does not require a manually specified base branch; the skill automatically detects the common base branch, such as main or master, before presenting integration options.