finishing-a-development-branch

To finalize a development branch after tests pass, the Skill presents explicit options for merging, creating a pull request, or cleaning up. It detects the base branch and suggests an appropriate workflow to safely complete the integration.

Base branch detection analyzes the repository state to determine the sensible target branch for integration. It then suggests the appropriate workflow, reducing manual decision-making across common multi-branch Git workflows.

Handling branch cleanup after merging is supported through optional cleanup steps offered during finalization. The Skill enforces safe completion by presenting explicit user choices for merging, pull requests, or branch deletion.

Yes, creating a pull request is one of the concrete finalization options presented after test verification. The Skill determines the appropriate base branch to target for the pull request workflow.

The workflow supports common multi-branch Git strategies by automatically determining a sensible base branch. This reduces manual decision-making when finalizing development branches across different project states.

Using explicit user choices when merging a git branch enforces safe completion by preventing accidental integrations. The Skill requires you to select a merge, pull request, or cleanup action to finalize the development branch.