finishing-a-development-branch

Merging a development branch involves verifying tests pass, determining the correct base branch, and choosing between local merge, creating a pull request, keeping the branch as-is, or discarding it. This skill automates those decisions and executes the selected action via git commands.

Complete integration requires mandatory test verification to prevent broken merges, structured options for merging locally or via pull request, and cleanup of associated worktrees. This skill guides you through all steps after implementation finishes.

Worktree cleanup integrates with git worktree management to safely remove temporary worktrees across local and remote workflows when work completes or is discarded. This skill handles cleanup as part of the branch completion process.

Yes. This skill automates the final merge or pull request workflow by determining the base branch, presenting four structured integration options, executing your selection via git and GitHub CLI, and cleaning up worktrees.

Inconsistent completion processes skip test verification or miss base-branch context. This skill enforces mandatory test checks before integration and provides structured options—merge locally, create a pull request, keep as-is, or discard—to prevent integration failures.

The choice depends on your workflow. This skill presents four options after test verification: merge locally, push and create a pull request for review, keep the branch unchanged, or discard it. You select based on your team's integration requirements.