finishing-a-development-branch

To safely merge a Git branch after passing tests, this skill validates your test results and pre-commit hooks, then presents four explicit options for merging, opening a PR, keeping, or discarding the branch.

The options for closing a Git feature branch include merging directly, creating a pull request, keeping the branch active, or discarding it entirely, all presented after automated test and pre-commit validation.

Yes, you can create an Azure Boards pull request when finishing a Git branch by selecting the PR creation option provided within the skill's guided post-implementation workflow.

To clean up Git worktrees and delete branches after merging, this skill manages branch deletion and worktree cleanup automatically as part of its workflow hygiene options.

Yes, this workflow enforces pre-commit checks before merging a PR by validating code quality hooks and ensuring all tests pass prior to presenting integration options.

Yes, you need standard Git tooling and repository access to execute this branch closing workflow, as it relies on native Git operations and pre-commit configurations.