finishing-a-development-branch

To finish a git feature branch, the skill verifies tests pass, then offers four structured merge options including local merge, push pull-request, keep as-is, or discard, followed by safe cleanup of worktrees and branches to ensure a clean repository state.

The best workflow options for merging a development branch include four deterministic choices: merge locally, push and create a pull-request, keep the branch as-is, or discard it entirely, reducing ambiguity and ensuring safe repository cleanup after integration.

Test verification before creating a pull request works by ensuring all tests pass on the feature branch before presenting any merge or pull-request workflow options, guaranteeing that only verified code is integrated into the mainline.

Yes, you can use this skill to discard a git branch and clean up worktrees, as it provides an explicit discard option among its four structured choices and executes safe repository cleanup of branches and artifacts after the chosen action.

If your feature branch is not ready for a pull request, you can select the keep as-is option from the four structured choices, preserving your current development state without triggering a merge or discarding your work.

To select the correct base branch when finishing development work, the skill guides base-branch selection during the final steps, ensuring your feature integrates into the appropriate mainline after test verification and before executing the chosen workflow.